View DSPIC30F5011-30IPT_6963731.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

? 2006 microchip technology inc. ds70117f dspic30f6011/6012/6013/6014 data sheet high-performance, 16-bit digital signal controllers
ds70117f-page ii ? 2006 microchip technology inc. information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. it is your responsibility to ensure that your application meets with your specifications. microchip makes no representations or warranties of any kind whether express or implied, written or oral, statutory or otherwise, related to the information, including but not limited to its condition, quality, performance, merchantability or fitness for purpose . microchip disclaims all liability arising from this information and its use. use of microchip devices in life support and/or safety applications is entirely at the buyer?s risk, and the buyer agrees to defend, indemnify and hold harmless microchip from any and all damages, claims, suits, or expenses resulting from such use. no licenses are conveyed, implicitly or otherwise, under any microchip intellectual property rights. trademarks the microchip name and logo, the microchip logo, accuron, dspic, k ee l oq , micro id , mplab, pic, picmicro, picstart, pro mate, powersmart, rfpic and smartshunt are registered trademarks of micr ochip technology incorporated in the u.s.a. and other countries. amplab, filterlab, migratable memory, mxdev, mxlab, seeval, smartsensor and the embedded control solutions company are registered trademarks of microchip technology incorporated in the u.s.a. analog-for-the-digital age, appl ication maestro, codeguard, dspicdem, dspicdem.net, dspicworks, ecan, economonitor, fansense, flexrom, fuzzylab, in-circuit serial programming, icsp, icepic, linear active thermistor, mindi, miwi, mpasm, mplib, mplink, pickit, picdem, picdem.net, piclab, pictail, powercal, powerinfo, powermate, powe rtool, real ice, rflab, rfpicdem, select mode, smart serial, smarttel, total endurance, uni/o, wiperlock and zena are trademarks of microchip technology incorporated in the u.s.a. and other countries. sqtp is a service mark of mi crochip technology incorporated in the u.s.a. all other trademarks mentioned herein are property of their respective companies. ? 2006, microchip technology incorporated, printed in the u.s.a., all rights reserved. printed on recycled paper. note the following details of the code protection feature on microchip devices: ? microchip products meet the specification cont ained in their particular microchip data sheet. ? microchip believes that its family of products is one of the mo st secure families of its kind on the market today, when used i n the intended manner and under normal conditions. ? there are dishonest and possibly illegal methods used to breach the code protection feature. all of these methods, to our knowledge, require using the microchip produc ts in a manner outside the operating specif ications contained in microchip?s data sheets. most likely, the person doing so is engaged in theft of intellectual property. ? microchip is willing to work with the customer who is concerned about the integrity of their code. ? neither microchip nor any other semiconductor manufacturer c an guarantee the security of their code. code protection does not mean that we are guaranteeing the product as ?unbreakable.? code protection is constantly evolving. we at microchip are co mmitted to continuously improvi ng the code protection features of our products. attempts to break microchip?s c ode protection feature may be a violation of the digital millennium copyright act. if such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that act. microchip received iso/ts-16949:2002 certification for its worldwide headquarters, design and wafer fabrication facilities in chandler and tempe, arizona, gresham, oregon and mountain view, california. the company?s quality system processes and procedures are for its pic ? 8-bit mcus, k ee l oq ? code hopping devices, serial eeproms, microperipherals, nonvolatile memory and analog products. in addition, microchip?s quality system for the design and manufacture of development systems is iso 9001:2000 certified.
? 2006 microchip technology inc. ds70117f-page 1 dspic30f6011/6012/6013/6014 high-performance modified risc cpu: ? modified harvard architecture ? c compiler optimized instruction set architecture ? flexible addressing modes ? 83 base instructions ? 24-bit wide instructions, 16-bit wide data path ? up to 144 kbytes on-chip flash program space ? up to 48k instruction words ? up to 8 kbytes of on-chip data ram ? up to 4 kbytes of nonvolatile data eeprom ? 16 x 16-bit working register array ? up to 30 mips operation: - dc to 40 mhz external clock input - 4 mhz-10 mhz oscillator input with pll active (4x, 8x, 16x) ? up to 41 interrupt sources: - 8 user-selectable priority levels - 5 external interrupt sources - 4 processor traps dsp features: ? dual data fetch ? modulo and bit-reversed modes ? two 40-bit wide accumulators with optional saturation logic ? 17-bit x 17-bit single cycle hardware fractional/ integer multiplier ? all dsp instructions are single cycle: - multiply-accumulate ( mac ) operation ? single-cycle 16 shift peripheral features: ? high current sink/source i/o pins: 25 ma/25 ma ? five 16-bit timers/counters; optionally pair up 16-bit timers into 32-bit timer modules ? 16-bit capture input functions ? 16-bit compare/pwm output functions ? data converter interface (dci) supports common audio codec protocols, including i 2 s and ac?97 ? 3-wire spi modules (supports 4 frame modes) ?i 2 c? module supports multi-master/slave mode and 7-bit/10-bit addressing ? two addressable uart modules with fifo buffers ? two can bus modules compliant with can 2.0b standard analog features: ? 12-bit analog-to-digital converter (adc) with: - 200 ksps conversion rate - up to 16 input channels - conversion available during sleep and idle ? programmable low-voltage detection (plvd) ? programmable brown-out reset special microcontroller features: ? enhanced flash program memory: - 10,000 erase/write cycle (min.) for industrial temperature range, 100k (typical) ? data eeprom memory: - 100,000 erase/write cycle (min.) for industrial temperature range, 1m (typical) ? self-reprogrammable under software control ? power-on reset (por), power-up timer (pwrt) and oscillator start-up timer (ost) ? flexible watchdog timer (wdt) with on-chip low power rc oscillator for reliable operation note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157). dspic30f6011/6012/6013/6014 high-performance digital signal controllers
dspic30f6011/6012/6013/6014 ds70117f-page 2 ? 2006 microchip technology inc. special microcontroller features (cont.): ? fail-safe clock monitor operation: - detects clock failure and switches to on-chip low power rc oscillator ? programmable code protection ? in-circuit serial programming? (icsp?) ? selectable power management modes: - sleep, idle and alternate clock modes cmos technology: ? low-power, high-speed flash technology ? wide operating voltage range (2.5v to 5.5v) ? industrial and extended temperature ranges ? low power consumption dspic30f6011/6012/6013/6014 controller families device pins program memory sram bytes eeprom bytes timer 16-bit input cap output comp/std pwm codec interface a/d 12-bit 200 ksps uart spi i 2 c ? can bytes instructions dspic30f6011 64 132k 44k 6144 2048 5 8 8 ? 16 ch 2 2 1 2 dspic30f6012 64 144k 48k 8192 4096 5 8 8 ac?97, i 2 s 16 ch 2 2 1 2 dspic30f6013 80 132k 44k 6144 2048 5 8 8 ? 16 ch 2 2 1 2 dspic30f6014 80 144k 48k 8192 4096 5 8 8 ac?97, i 2 s 16 ch 2 2 1 2
? 2006 microchip technology inc. ds70117f-page 3 dspic30f6011/6012/6013/6014 pin diagrams note: for descriptions of individual pins, see section 1.0 ?device overview? . 1 2 3 4 5 6 7 8 9 10 11 12 13 36 35 34 33 32 31 30 29 28 27 26 64 63 62 61 60 59 58 57 56 14 15 16 17 18 19 20 21 22 23 24 25 emuc1/sosco/t1ck/cn0/rc14 emud1/sosci/t4ck/cn1/rc13 emuc2/oc1/rd0 ic4/int4/rd11 ic2/int2/rd9 ic1/int1/rd8 v ss osc2/clko/rc15 osc1/clki v dd scl/rg2 emuc3/sck1/int0/rf6 u1rx/sdi1/rf2 emud3/u1tx/sdo1/rf3 rg15 t2ck/rc1 t3ck/rc2 sck2/cn8/rg6 sdi2/cn9/rg7 sdo2/cn10/rg8 mclr v ss v dd an3/cn5/rb3 an2/ss1 /lvdin/cn4/rb2 pgc/emuc/an1/v ref -/cn3/rb1 pgd/emud/an0/v ref +/cn2/rb0 oc8/cn16/rd7 rg13 rg12 rg14 v ss c2tx/rg1 c1tx/rf1 c2rx/rg0 emud2/oc2/rd1 oc3/rd2 an6/ocfa/rb6 an7/rb7 av dd av ss an8/rb8 an9/rb9 an10/rb10 an11/rb11 v ss v dd an12/rb12 an13/rb13 an14/rb14 an15/ocfb/cn12/rb15 u2tx/cn18/rf5 u2rx/cn17/rf4 sda/rg3 43 42 41 40 39 38 37 44 48 47 46 50 49 51 54 53 52 55 45 ss2 /cn11/rg9 an5/ic8/cn7/rb5 an4/ic7/cn6/rb4 ic3/int3/rd10 v dd c1rx/rf0 oc4/rd3 oc7/cn15/rd6 oc6/ic6/cn14/rd5 oc5/ic5/cn13/rd4 64-pin tqfp dspic30f6011 *dspic30f6011a recommended for new designs
dspic30f6011/6012/6013/6014 ds70117f-page 4 ? 2006 microchip technology inc. pin diagrams (continued) note: for descriptions of individual pins, see section 1.0 ?device overview? . 1 2 3 4 5 6 7 8 9 10 11 12 13 36 35 34 33 32 31 30 29 28 27 26 64 63 62 61 60 59 58 57 56 14 15 16 17 18 19 20 21 22 23 24 25 emuc1/sosco/t1ck/cn0/rc14 emud1/sosci/t4ck/cn1/rc13 emuc2/oc1/rd0 ic4/int4/rd11 ic2/int2/rd9 ic1/int1/rd8 v ss osc2/clko/rc15 osc1/clki v dd scl/rg2 emuc3/sck1/int0/rf6 u1rx/sdi1/rf2 emud3/u1tx/sdo1/rf3 cofs/rg15 t2ck/rc1 t3ck/rc2 sck2/cn8/rg6 sdi2/cn9/rg7 sdo2/cn10/rg8 mclr v ss v dd an3/cn5/rb3 an2/ss1 /lvdin/cn4/rb2 pgc/emuc/an1/v ref -/cn3/rb1 pgd/emud/an0/v ref +/cn2/rb0 oc8/cn16/rd7 csdo/rg13 csdi/rg12 csck/rg14 v ss c2tx/rg1 c1tx/rf1 c2rx/rg0 emud2/oc2/rd1 oc3/rd2 an6/ocfa/rb6 an7/rb7 av dd av ss an8/rb8 an9/rb9 an10/rb10 an11/rb11 v ss v dd an12/rb12 an13/rb13 an14/rb14 an15/ocfb/cn12/rb15 u2tx/cn18/rf5 u2rx/cn17/rf4 sda/rg3 43 42 41 40 39 38 37 44 48 47 46 50 49 51 54 53 52 55 45 ss2 /cn11/rg9 an5/ic8/cn7/rb5 an4/ic7/cn6/rb4 ic3/int3/rd10 v dd c1rx/rf0 oc4/rd3 oc7/cn15/rd6 oc6/ic6/cn14/rd5 oc5/ic5/cn13/rd4 64-pin tqfp dspic30f6012 *dspic30f6012a recommended for new designs
? 2006 microchip technology inc. ds70117f-page 5 dspic30f6011/6012/6013/6014 pin diagrams (continued) note: for descriptions of individual pins, see section 1.0 ?device overview? . 72 74 73 71 70 69 68 67 66 65 64 63 62 61 20 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 50 49 48 47 46 45 44 21 41 40 39 38 37 36 35 34 23 24 25 26 27 28 29 30 31 32 33 17 18 19 75 1 57 56 55 54 53 52 51 60 59 58 43 42 76 78 77 79 22 80 ic5/rd12 oc4/rd3 oc3/rd2 emud2/oc2/rd1 rg14 cn23/ra7 cn22/ra6 c2rx/rg0 c2tx/rg1 c1tx/rf1 c1rx/rf0 rg13 rg12 oc8/cn16/rd7 oc6/cn14/rd5 emuc2/oc1/rd0 ic4/rd11 ic2/rd9 ic1/rd8 int4/ra15 ic3/rd10 int3/ra14 v ss osc1/clki v dd scl/rg2 u1rx/rf2 u1tx/rf3 emuc1/sosco/t1ck/cn0/rc14 emud1/sosci/cn1/rc13 v ref +/ra10 v ref -/ra9 av dd av ss an8/rb8 an9/rb9 an10/rb10 an11/rb11 v dd u2rx/cn17/rf4 ic8/cn21/rd15 u2tx/cn18/rf5 an6/ocfa/rb6 an7/rb7 t3ck/rc2 t4ck/rc3 t5ck/rc4 sck2/cn8/rg6 sdi2/cn9/rg7 sdo2/cn10/rg8 mclr ss2 /cn11/rg9 an4/cn6/rb4 an3/cn5/rb3 an2/ss1 /lvdin/cn4/rb2 pgc/emuc/an1/cn3/rb1 pgd/emud/an0/cn2/rb0 v ss v dd rg15 t2ck/rc1 int2/ra13 int1/ra12 an12/rb12 an13/rb13 an14/rb14 an15/ocfb/cn12/rb15 v dd v ss oc5/cn13/rd4 ic6/cn19/rd13 sda/rg3 sdi1/rf7 emud3/sdo1/rf8 an5/cn7/rb5 v ss osc2/clko/rc15 oc7/cn15/rd6 emuc3/sck1/int0/rf6 ic7/cn20/rd14 80-pin tqfp dspic30f6013 *dspic30f6013a recommended for new designs
dspic30f6011/6012/6013/6014 ds70117f-page 6 ? 2006 microchip technology inc. pin diagrams (continued) note: for descriptions of individual pins, see section 1.0 ?device overview? . 72 74 73 71 70 69 68 67 66 65 64 63 62 61 20 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 50 49 48 47 46 45 44 21 41 40 39 38 37 36 35 34 23 24 25 26 27 28 29 30 31 32 33 17 18 19 75 1 57 56 55 54 53 52 51 60 59 58 43 42 76 78 77 79 22 80 ic5/rd12 oc4/rd3 oc3/rd2 emud2/oc2/rd1 csck/rg14 c2rx/rg0 c2tx/rg1 c1tx/rf1 c1rx/rf0 csdo/rg13 csdi/rg12 oc8/cn16/rd7 oc6/cn14/rd5 emuc2/oc1/rd0 ic4/rd11 ic2/rd9 ic1/rd8 int4/ra15 ic3/rd10 int3/ra14 v ss osc1/clki v dd scl/rg2 u1rx/rf2 u1tx/rf3 emuc1/sosco/t1ck/cn0/rc14 emud1/sosci/cn1/rc13 v ref +/ra10 v ref -/ra9 av dd av ss an8/rb8 an9/rb9 an10/rb10 an11/rb11 v dd u2rx/cn17/rf4 ic8/cn21/rd15 u2tx/cn18/rf5 an6/ocfa/rb6 an7/rb7 t3ck/rc2 t4ck/rc3 t5ck/rc4 sck2/cn8/rg6 sdi2/cn9/rg7 sdo2/cn10/rg8 mclr ss2 /cn11/rg9 an4/cn6/rb4 an3/cn5/rb3 an2/ss1 /lvdin/cn4/rb2 pgc/emuc/an1/cn3/rb1 pgd/emud/an0/cn2/rb0 v ss v dd cofs/rg15 t2ck/rc1 int2/ra13 int1/ra12 an12/rb12 an13/rb13 an14/rb14 an15/ocfb/cn12/rb15 v dd v ss oc5/cn13/rd4 ic6/cn19/rd13 sda/rg3 sdi1/rf7 emud3/sdo1/rf8 an5/cn7/rb5 v ss osc2/clko/rc15 oc7/cn15/rd6 emuc3/sck1/int0/rf6 ic7/cn20/rd14 80-pin tqfp dspic30f6014 cn23/ra7 cn22/ra6 *dspic30f6014a recommended for new designs
? 2006 microchip technology inc. ds70117f-page 7 dspic30f6011/6012/6013/6014 table of contents 1.0 device overview ............................................................................................................. ............................................................. 9 2.0 cpu architecture overview................................................................................................... ..................................................... 15 3.0 memory organization ......................................................................................................... ........................................................ 25 4.0 address generator units..................................................................................................... ....................................................... 39 5.0 interrupts .................................................................................................................. .................................................................. 45 6.0 flash program memory........................................................................................................ ...................................................... 51 7.0 data eeprom memory .......................................................................................................... ................................................... 57 8.0 i/o ports ................................................................................................................... .................................................................. 63 9.0 timer1 module ............................................................................................................... ............................................................ 69 10.0 timer2/3 module ............................................................................................................ ............................................................ 73 11.0 timer4/5 module ........................................................................................................... ............................................................ 79 12.0 input capture module....................................................................................................... .......................................................... 83 13.0 output compare module ...................................................................................................... ...................................................... 87 14.0 spi module................................................................................................................. ................................................................ 91 15.0 i2c module ................................................................................................................. ................................................................ 95 16.0 universal asynchronous receiver transmitter (uart) module .................................................................. ............................ 103 17.0 can module ................................................................................................................. ............................................................ 111 18.0 data converter interface (dci) module...................................................................................... .............................................. 125 19.0 12-bit analog-to-digital converter (a/d) module............................................................................ .......................................... 135 20.0 system integration ......................................................................................................... .......................................................... 145 21.0 instruction set summary .................................................................................................... ...................................................... 161 22.0 development support........................................................................................................ ....................................................... 169 23.0 electrical characteristics ................................................................................................. ......................................................... 173 24.0 packaging information...................................................................................................... ........................................................ 211 appendix a: revision history................................................................................................... .......................................................... 215 index .......................................................................................................................... ........................................................................ 217 the microchip web site ......................................................................................................... ............................................................ 223 customer change notification service ........................................................................................... ................................................... 223 customer support............................................................................................................... ............................................................... 223 reader response ................................................................................................................ .............................................................. 224 product identification system .................................................................................................. .......................................................... 225 to our valued customers it is our intention to provide our valued customers with the best documentation possible to ensure successful use of your micro chip products. to this end, we will continue to improve our publications to better suit your needs. our publications will be refined and enhanced as new volumes and updates are introduced. if you have any questions or comments regar ding this publication, please contact the marketing communications department via e-mail at docerrors@microchip.com or fax the reader response form in the back of this data sheet to (480) 792-4150. we welcome your feedback. most current data sheet to obtain the most up-to-date version of this data s heet, please register at our worldwide web site at: http://www.microchip.com you can determine the version of a data sheet by examining its literature number found on the bottom outside corner of any page . the last character of the literature number is the vers ion number, (e.g., ds30000a is version a of document ds30000). errata an errata sheet, describing minor operational differences fr om the data sheet and recommended workarounds, may exist for curren t devices. as device/doc umentation issues become known to us, we will publis h an errata sheet. the errata will specify the revisi on of silicon and revision of document to which it applies. to determine if an errata sheet exists for a particul ar device, please check with one of the following: ? microchip?s worldwide web site; http://www.microchip.com ? your local microchip sales office (see last page) when contacting a sales office, please spec ify which device, revision of silicon and data sheet (include literature number) you are using. customer notification system register on our web site at www.microchip.com to receive the most current information on all of our products.
dspic30f6011/6012/6013/6014 ds70117f-page 8 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 9 dspic30f6011/6012/6013/6014 1.0 device overview this document contains specific information for the dspic30f6011/6012/6013/6014 digital signal control- ler (dsc) devices. the dspic30f devices contain extensive digital signal processor (dsp) functionality within a high-performance 16-bit microcontroller (mcu) architecture. figure 1-1 and figure 1-2 show device block diagrams for dspic30f6011/6012 and dspic30f6013/6014 respectively. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157).
dspic30f6011/6012/6013/6014 ds70117f-page 10 ? 2006 microchip technology inc. figure 1-1: dspic30f6011/6012 block diagram an8/rb8 an9/rb9 an10/rb10 an11/rb11 power-up timer oscillator start-up timer por/bor reset watchdog timer instruction decode & control osc1/clki mclr v dd , v ss an4/ic7/cn6/rb4 an12/rb12 an13/rb13 an14/rb14 an15/ocfb/cn12/rb15 low-voltage detect uart1, can2 timing generation can1, an5/ic8/cn7/rb5 16 pch pcl program counter alu<16> 16 24 24 24 24 x data bus ir i 2 c? dci an6/ocfa/rb6 an7/rb7 pcu 12-bit adc timers sck2/cn8/rg6 sdi2/cn9/rg7 sdo2/cn10/rg8 ss2 /cn11/rg9 input capture module output compare module emuc1/sosco/t1ck/cn0/rc14 emud1/sosci/t4ck/cn1/rc13 t2ck/rc1 portb c2rx/rg0 c2tx/rg1 scl/rg2 sda/rg3 portg portd 16 16 16 16 x 16 w reg array divide unit engine dsp decode rom latch 16 y data bus effective address x ragu x wagu y agu pgd/emud/an0/v ref +/cn2/rb0 pgc/emuc/an1/v ref -/cn3/rb1 an2/ss1 /lvdin/cn4/rb2 an3/cn5/rb3 osc2/clko/rc15 av dd , av ss uart2 spi2 16 16 16 16 16 portc 16 16 16 16 8 interrupt controller psv & table data access control block stack control logic loop control logic data latch data latch y data ram x data ram address latch address latch control signals to various blocks emuc2/oc1/rd0 emud2/oc2/rd1 oc3/rd2 oc4/rd3 oc5/ic5/cn13/rd4 oc6/ic6/cn14/rd5 oc7/cn15/rd6 oc8/cn16/rd7 ic1/int1/rd8 ic2/int2/rd9 ic3/int3/rd10 ic4/int4/rd11 16 csdi*/rg12 csdo*/rg13 csck*/rg14 cofs*/rg15 t3ck/rc2 spi1, address latch program memory (up to 144 kbytes) data latch data eeprom (up to 4 kbytes) 16 u2tx/cn18/rf5 emuc3/sck1/int0/rf6 c1rx/rf0 c1tx/rf1 u1rx/sdi1/rf2 emud3/u1tx/sdo1/rf3 u2rx/cn17/rf4 portf *present in the dspic30f6012 only.
? 2006 microchip technology inc. ds70117f-page 11 dspic30f6011/6012/6013/6014 figure 1-2: dspic30f6013/6014 block diagram an8/rb8 an9/rb9 an10/rb10 an11/rb11 power-up timer oscillator start-up timer por/bor reset watchdog timer instruction decode & control osc1/clki mclr v dd , v ss an4/cn6/rb4 an12/rb12 an13/rb13 an14/rb14 an15/ocfb/cn12/rb15 low-voltage detect uart1, int4/ra15 int3/ra14 v ref +/ra10 v ref -/ra9 can2 timing generation can1, an5/cn7/rb5 16 pch pcl program counter alu<16> 16 24 24 24 24 x data bus ir i 2 c? dci an6/ocfa/rb6 an7/rb7 pcu 12-bit adc timers sck2/cn8/rg6 sdi2/cn9/rg7 sdo2/cn10/rg8 ss2 /cn11/rg9 u2tx/cn18/rf5 emuc3/sck1/int0/rf6 sdi1/rf7 emud3/sdo1/rf8 input capture module output compare module emuc1/sosco/t1ck/cn0/rc14 emud1/sosci/cn1/rc13 t4ck/rc3 t2ck/rc1 portb c1rx/rf0 c1tx/rf1 u1rx/rf2 u1tx/rf3 c2rx/rg0 c2tx/rg1 scl/rg2 sda/rg3 portg portd 16 16 16 16 x 16 w reg array divide unit engine dsp decode rom latch 16 y data bus effective address x ragu x wagu y agu pgd/emud/an0/cn2/rb0 pgc/emuc/an1/cn3/rb1 an2/ss1 /lvdin/cn4/rb2 an3/cn5/rb3 osc2/clko/rc15 u2rx/cn17/rf4 av dd , av ss uart2 spi2 16 16 16 16 16 porta portc portf 16 16 16 16 8 interrupt controller psv & table data access control block stack control logic loop control logic data latch data latch y data ram x data ram address latch address latch control signals to various blocks emuc2/oc1/rd0 emud2/oc2/rd1 oc3/rd2 oc4/rd3 oc5/cn13/rd4 oc6/cn14/rd5 oc7/cn15/rd6 oc8/cn16/rd7 ic1/rd8 ic2/rd9 ic3/rd10 ic4/rd11 ic5/rd12 ic6/cn19/rd13 ic7/cn20/rd14 ic8/cn21/rd15 16 csdi*/rg12 csdo*/rg13 csck*/rg14 cofs*/rg15 t3ck/rc2 spi1, int1/ra12 int2/ra13 cn23/ra7 cn22/ra6 t5ck/rc4 address latch program memory (up to 144 kbytes) data latch data eeprom (up to 4 kbytes) 16 *present in the dspic30f6014 only.
dspic30f6011/6012/6013/6014 ds70117f-page 12 ? 2006 microchip technology inc. table 1-1 provides a brief description of device i/o pinouts and the functions that may be multiplexed to a port pin. multiple functions may exist on one port pin. when multiplexing occurs, the peripheral module?s functional requirements may force an override of the data direction of the port pin. table 1-1: pinout i/o descriptions pin name pin type buffer type description an0-an15 i analog analog input channels. an0 and an1 are also used for device programming data and clock inputs, respectively. av dd p p positive supply for analog module. av ss p p ground reference for analog module. clki clko i o st/cmos ? external clock source input. always associated with osc1 pin function. oscillator crystal output. connects to crystal or resonator in crystal oscillator mode. optionally functions as clko in rc and ec modes. always associated with osc2 pin function. cn0-cn23 i st input change notification inputs. can be software programmed for internal weak pull-ups on all inputs. cofs csck csdi csdo i/o i/o i o st st st ? data converter interface frame synchronization pin. data converter interface serial clock input/output pin. data converter interface serial data input pin. data converter interface serial data output pin. c1rx c1tx c2rx c2tx i o i o st ? st ? can1 bus receive pin. can1 bus transmit pin. can2 bus receive pin. can2 bus transmit pin emud emuc emud1 emuc1 emud2 emuc2 emud3 emuc3 i/o i/o i/o i/o i/o i/o i/o i/o st st st st st st st st icd primary communication channel data input/output pin. icd primary communication channel clock input/output pin. icd secondary communication channel data input/output pin. icd secondary communication channel clock input/output pin. icd tertiary communication channel data input/output pin. icd tertiary communication channel clock input/output pin. icd quaternary communication channel data input/output pin. icd quaternary communication channel clock input/output pin. ic1-ic8 i st capture inputs 1 through 8. int0 int1 int2 int3 int4 i i i i i st st st st st external interrupt 0. external interrupt 1. external interrupt 2. external interrupt 3. external interrupt 4. lvdin i analog low-voltage detect reference voltage input pin. mclr i/p st master clear (reset) input or programming voltage input. this pin is an active low reset to the device. ocfa ocfb oc1-oc8 i i o st st ? compare fault a input (for compare channels 1, 2, 3 and 4). compare fault b input (for compare channels 5, 6, 7 and 8). compare outputs 1 through 8. legend: cmos = cmos compatible input or output analog = analog input st = schmitt trigger input with cmos levels o = output i = input p = power
? 2006 microchip technology inc. ds70117f-page 13 dspic30f6011/6012/6013/6014 osc1 osc2 i i/o st/cmos ? oscillator crystal input. st buffer when configured in rc mode; cmos otherwise. oscillator crystal output. connects to crystal or resonator in crystal oscillator mode. optionally functions as clko in rc and ec modes. pgd pgc i/o i st st in-circuit serial programming data input/output pin. in-circuit serial programming clock input pin. ra6-ra7 ra9-ra10 ra12-ra15 i/o i/o i/o st st st porta is a bidirectional i/o port. rb0-rb15 i/o st portb is a bidirectional i/o port. rc1-rc4 rc13-rc15 i/o i/o st st portc is a bidirectional i/o port. rd0-rd15 i/o st portd is a bidirectional i/o port. rf0-rf8 i/o st portf is a bidirectional i/o port. rg0-rg3 rg6-rg9 rg12-rg15 i/o i/o i/o st st st portg is a bidirectional i/o port. sck1 sdi1 sdo1 ss1 sck2 sdi2 sdo2 ss2 i/o i o i i/o i o i st st ? st st st ? st synchronous serial clock input/output for spi1. spi1 data in. spi1 data out. spi1 slave synchronization. synchronous serial clock input/output for spi2. spi2 data in. spi2 data out. spi2 slave synchronization. scl sda i/o i/o st st synchronous serial clock input/output for i 2 c?. synchronous serial data input/output for i 2 c. sosco sosci o i ? st/cmos 32 khz low power oscillator crystal output. 32 khz low power oscillator crystal input. st buffer when configured in rc mode; cmos otherwise. t1ck t2ck t3ck t4ck t5ck i i i i i st st st st st timer1 external clock input. timer2 external clock input. timer3 external clock input. timer4 external clock input. timer5 external clock input. u1rx u1tx u1arx u1atx u2rx u2tx i o i o i o st ? st ? st ? uart1 receive. uart1 transmit. uart1 alternate receive. uart1 alternate transmit. uart2 receive. uart2 transmit. v dd p ? positive supply for logic and i/o pins. v ss p ? ground reference for logic and i/o pins. v ref + i analog analog voltage reference (high) input. v ref - i analog analog voltage reference (low) input. table 1-1: pinout i/o descriptions (continued) pin name pin type buffer type description legend: cmos = cmos compatible input or output analog = analog input st = schmitt trigger input with cmos levels o = output i = input p = power
dspic30f6011/6012/6013/6014 ds70117f-page 14 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 15 dspic30f6011/6012/6013/6014 2.0 cpu architecture overview 2.1 core overview this section contains a brief overview of the cpu architecture of the dspic30f. for additional hard- ware and programming information, please refer to the ? dspic30f family reference manual? (ds70046) and the ? dspic30f/33f programmer?s reference manual ? (ds70157) respectively. the core has a 24-bit instruction word. the program counter (pc) is 23 bits wide with the least significant bit (lsb) always clear (refer to section 3.1 ?program address space? ), and the most significant bit (msb) is ignored during normal program execution, except for certain specialized instructions. thus, the pc can address up to 4m instruction words of user program space. an instruction prefetch mechanism is used to help maintain throughput. program loop constructs, free from loop count management overhead, are sup- ported using the do and repeat instructions, both of which are interruptible at any point. the working register array consists of 16 x 16-bit regis- ters, each of which can act as data, address or offset registers. one working register (w15) operates as a software stack pointer for interrupts and calls. the data space is 64 kbytes (32k words) and is split into two blocks, referred to as x and y data memory. each block has its own independent address genera- tion unit (agu). most instructions operate solely through the x memory, agu, which provides the appearance of a single unified data space. the multiply-accumulate ( mac ) class of dual source dsp instructions operate through both the x and y agus, splitting the data address space into two parts (see section 3.2 ?data address space? ). the x and y data space boundary is device specific and cannot be altered by the user. each data word consists of 2 bytes, and most instructions can address data either as words or bytes. there are two methods of accessing data stored in program memory: ? the upper 32 kbytes of data space memory can be mapped into the lower half (user space) of pro- gram space at any 16k program word boundary, defined by the 8-bit program space visibility page (psvpag) register. this lets any instruction access program space as if it were data space, with a limitation that the access requires an addi- tional cycle. moreover, only the lower 16 bits of each instruction word can be accessed using this method. ? linear indirect access of 32k word pages within program space is also possible using any working register, via table read and write instructions. table read and write instructions can be used to access all 24 bits of an instruction word. overhead-free circular buffers (modulo addressing) are supported in both x and y address spaces. this is primarily intended to remove the loop overhead for dsp algorithms. the x agu also supports bit-reversed addressing on destination effective addresses to greatly simplify input or output data reordering for radix-2 fft algorithms. refer to section 4.0 ?address generator units? for details on modulo and bit-reversed addressing. the core supports inherent (no operand), relative, literal, memory direct, register direct, register indirect, register offset and literal offset addressing modes. instructions are associated with predefined addressing modes, depending upon their functional requirements. for most instructions, the core is capable of executing a data (or program data) memory read, a working reg- ister (data) read, a data memory write and a program (instruction) memory read per instruction cycle. as a result, 3-operand instructions are supported, allowing c = a + b operations to be executed in a single cycle. a dsp engine has been included to significantly enhance the core arithmetic capability and throughput. it features a high-speed 17-bit by 17-bit multiplier, a 40-bit alu, two 40-bit saturating accumulators and a 40-bit bidirectional barrel shifter. data in the accumula- tor or any working register can be shifted up to 15 bits right, or 16 bits left in a single cycle. the dsp instruc- tions operate seamlessly with all other instructions and have been designed for optimal real-time performance. the mac class of instructions can concurrently fetch two data operands from memory while multiplying two w registers. to enable this concurrent fetching of data operands, the data space has been split for these instructions and linear for all others. this has been achieved in a transparent and flexible manner, by ded- icating certain working registers to each address space for the mac class of instructions. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157).
dspic30f6011/6012/6013/6014 ds70117f-page 16 ? 2006 microchip technology inc. the core does not support a multi-stage instruction pipeline. however, a single stage instruction prefetch mechanism is used, which accesses and partially decodes instructions a cycle ahead of execution, in order to maximize available execution time. most instructions execute in a single cycle with certain exceptions. the core features a vectored exception processing structure for traps and interrupts, with 62 independent vectors. the exceptions consist of up to 8 traps (of which 4 are reserved) and 54 interrupts. each interrupt is prioritized based on a user assigned priority between 1 and 7 (1 being the lowest priority and 7 being the highest), in conjunction with a predetermined ?natural order?. traps have fixed priorities ranging from 8 to 15. 2.2 programmer?s model the programmer?s model is shown in figure 2-1 and consists of 16 x 16-bit working registers (w0 through w15), 2 x 40-bit accumulators (acca and accb), status register (sr), data table page register (tblpag), program space visibility page register (psvpag), do and repeat registers (dostart, doend, dcount and rcount) and program counter (pc). the working registers can act as data, address or offset registers. all registers are memory mapped. w0 acts as the w register for file register addressing. some of these registers have a shadow register asso- ciated with each of them, as shown in figure 2-1. the shadow register is used as a temporary holding register and can transfer its contents to or from its host register upon the occurrence of an event. none of the shadow registers are accessible directly. the following rules apply for transfer of registers into and out of shadows. ? push.s and pop.s w0, w1, w2, w3, sr (dc, n, ov, z and c bits only) are transferred. ? do instruction dostart, doend, dcount shadows are pushed on loop start, and popped on loop end. when a byte operation is performed on a working reg- ister, only the least significant byte (lsb) of the target register is affected. however, a benefit of memory mapped working registers is that both the least and most significant bytes can be manipulated through byte wide data memory space accesses. 2.2.1 software stack pointer/ frame pointer the dspic ? dsc devices contain a software stack. w15 is the dedicated software stack pointer (sp), and will be automatically modified by exception processing and subroutine calls and returns. however, w15 can be referenced by any instruction in the same manner as all other w registers. this simplifies the reading, writing and manipulation of the stack pointer (e.g., creating stack frames). w15 is initialized to 0x0800 during a reset. the user may reprogram the sp during initialization to any location within data space. w14 has been dedicated as a stack frame pointer as defined by the lnk and ulnk instructions. however, w14 can be referenced by any instruction in the same manner as all other w registers. 2.2.2 status register the dspic dsc core has a 16-bit status register (sr), the lsb of which is referred to as the sr low byte (srl) and the most significant byte (msb) as the sr high byte (srh). see figure 2-1 for sr layout. srl contains all the mcu alu operation status flags (including the z bit), as well as the cpu interrupt prior- ity level status bits, ipl<2:0> and the repeat active status bit, ra. during exception processing, srl is concatenated with the msb of the pc to form a complete word value which is then stacked. the upper byte of the status register contains the dsp adder/subtracter status bits, the do loop active bit (da) and the digit carry (dc) status bit. 2.2.3 program counter the program counter is 23 bits wide; bit 0 is always clear. therefore, the pc can address up to 4m instruction words. note: in order to protect against misaligned stack accesses, w15<0> is always clear.
? 2006 microchip technology inc. ds70117f-page 17 dspic30f6011/6012/6013/6014 figure 2-1: programmer?s model tabpag pc22 pc0 7 0 d0 d15 program counter data table page address status register working registers dsp operand registers w1 w2 w3 w4 w5 w6 w7 w8 w9 w10 w11 w12/dsp offset w13/dsp write back w14/frame pointer w15/stack pointer dsp address registers ad39 ad0 ad31 dsp accumulators acca accb psvpag 7 0 program space visibility page address z 0 oa ob sa sb rcount 15 0 repeat loop counter dcount 15 0 do loop counter dostart 22 0 do loop start address ipl2 ipl1 splim stack pointer limit register ad15 srl push.s shadow do shadow oab sab 15 0 core configuration register legend corcon da dc ra n tblpag psvpag ipl0 ov w0/wreg srh do loop end address doend 22 c
dspic30f6011/6012/6013/6014 ds70117f-page 18 ? 2006 microchip technology inc. 2.3 divide support the dspic dsc devices feature a 16/16-bit signed fractional divide operation, as well as 32/16-bit and 16/ 16-bit signed and unsigned integer divide operations, in the form of single instruction iterative divides. the fol- lowing instructions and data sizes are supported: 1. divf - 16/16 signed fractional divide 2. div.sd - 32/16 signed divide 3. div.ud - 32/16 unsigned divide 4. div.sw - 16/16 signed divide 5. div.uw - 16/16 unsigned divide the 16/16 divides are similar to the 32/16 (same number of iterations), but the dividend is either zero-extended or sign-extended during the first iteration. the divide instructions must be executed within a repeat loop. any other form of execution (e.g., a series of discrete divide instructions) will not function correctly because the instruction flow depends on rcount. the divide instruction does not automatically set up the rcount value and it must, therefore, be explicitly and correctly specified in the repeat instruc- tion as shown in table 2-1 ( repeat will execute the tar- get instruction {operand value + 1} times). the repeat loop count must be setup for 18 iterations of the div/ divf instruction. thus, a complete divide operation requires 19 cycles. table 2-1: divide instructions note: the divide flow is interruptible. however, the user needs to save the context as appropriate. instruction function divf signed fractional divide: wm/wn w0; rem w1 div.sd signed divide: (wm + 1:wm)/wn w0; rem w1 div.ud unsigned divide: (wm + 1:wm/wn w0; rem w 1 div.sw signed divide: wm/wn w0; rem w1 div.uw unsigned divide: wm/wn w0; rem w1
? 2006 microchip technology inc. ds70117f-page 19 dspic30f6011/6012/6013/6014 2.4 dsp engine the dsp engine consists of a high-speed 17-bit x 17-bit multiplier, a barrel shifter and a 40-bit adder/ subtracter (with two target accumulators, round and saturation logic). the dspic30f is a single-cycle instruction flow archi- tecture, therefore, concurrent operation of the dsp engine with mcu instruction flow is not possible. however, some mcu alu and dsp engine resources may be used concurrently by the same instruction (e.g., ed, edac). the dsp engine also has the capability to perform inherent accumulator-to-accumulator operations, which require no additional data. these instructions are add, sub and neg . the dsp engine has various options selected through various bits in the cpu core configuration register (corcon), as listed below: 1. fractional or integer dsp multiply (if). 2. signed or unsigned dsp multiply (us). 3. conventional or convergent rounding (rnd). 4. automatic saturation on/off for acca (sata). 5. automatic saturation on/off for accb (satb). 6. automatic saturation on/off for writes to data memory (satdw). 7. accumulator saturation mode selection (accsat). a block diagram of the dsp engine is shown in figure 2-2. note: for corcon layout, see table 3-3. table 2-2: dsp instructions summary instruction algebraic operation acc wb? clr a = 0 yes ed a = (x ? y) 2 no edac a = a + (x ? y) 2 no mac a = a + (x * y) yes mac a = a + x 2 no movsac no change in a yes mpy a = x * y no mpy.n a = ? x * y no msc a = a ? x * y yes
dspic30f6011/6012/6013/6014 ds70117f-page 20 ? 2006 microchip technology inc. figure 2-2: dsp engine block diagram zero backfill sign-extend barrel shifter 40-bit accumulator a 40-bit accumulator b round logic x data bus to/from w array adder saturate negate 32 32 33 16 16 16 16 40 40 40 40 s a t u r a t e y data bus 40 carry/borrow out carry/borrow in 16 40 multiplier/scaler 17-bit
? 2006 microchip technology inc. ds70117f-page 21 dspic30f6011/6012/6013/6014 2.4.1 multiplier the 17 x 17-bit multiplier is capable of signed or unsigned operation and can multiplex its output using a scaler to support either 1.31 fractional (q31) or 32-bit integer results. unsigned operands are zero-extended into the 17th bit of the multiplier input value. signed operands are sign-extended into the 17th bit of the mul- tiplier input value. the output of the 17 x 17-bit multi- plier/scaler is a 33-bit value which is sign-extended to 40 bits. integer data is inherently represented as a signed two?s complement value, where the msb is defined as a sign bit. generally speaking, the range of an n-bit two?s complement integer is -2 n-1 to 2 n-1 ? 1. for a 16-bit integer, the data range is -32768 (0x8000) to 32767 (0x7fff) including ? 0 ?. for a 32-bit integer, the data range is -2,147,483,648 (0x8000 0000) to 2,147,483,645 (0x7fff ffff). when the multiplier is configured for fractional multipli- cation, the data is represented as a two?s complement fraction, where the msb is defined as a sign bit and the radix point is implied to lie just after the sign bit (qx for- mat). the range of an n-bit two?s complement fraction with this implied radix point is -1.0 to (1 ? 2 1-n ). for a 16-bit fraction, the q15 data range is -1.0 (0x8000) to 0.999969482 (0x7fff) including ? 0 ? and has a preci- sion of 3.01518x10 -5 . in fractional mode, the 16x16 multiply operation generates a 1.31 product which has a precision of 4.65661 x 10 -10 . the same multiplier is used to support the mcu multi- ply instructions which include integer 16-bit signed, unsigned and mixed sign multiplies. the mul instruction may be directed to use byte or word sized operands. byte operands will direct a 16-bit result, and word operands will direct a 32-bit result to the specified register(s) in the w array. 2.4.2 data accumulators and adder/subtracter the data accumulator consists of a 40-bit adder/ subtracter with automatic sign extension logic. it can select one of two accumulators (a or b) as its pre- accumulation source and post-accumulation destina- tion. for the add and lac instructions, the data to be accumulated or loaded can be optionally scaled via the barrel shifter, prior to accumulation. 2.4.2.1 adder/subtracter, overflow and saturation the adder/subtracter is a 40-bit adder with an optional zero input into one side and either true, or complement data into the other input. in the case of addition, the carry/borrow input is active high and the other input is true data (not complemented), whereas in the case of subtraction, the carry/borrow input is active low and the other input is complemented. the adder/subtracter generates overflow status bits sa/sb and oa/ob, which are latched and reflected in the status register: ? overflow from bit 39: this is a catastrophic overflow in which the sign of the accumulator is destroyed. ? overflow into guard bits 32 through 39: this is a recoverable overflow. this bit is set whenever all the guard bits bits are not identical to each other. the adder has an additional saturation block which controls accumulator data saturation, if selected. it uses the result of the adder, the overflow status bits described above, and the sata/b (corcon<7:6>) and accsat (corcon<4>) mode control bits to determine when and to what value to saturate. six status register bits have been provided to support saturation and overflow; they are: 1. oa: acca overflowed into guard bits 2. ob: accb overflowed into guard bits 3. sa: acca saturated (bit 31 overflow and saturation) or acca overflowed into guard bits and saturated (bit 39 overflow and saturation) 4. sb: accb saturated (bit 31 overflow and saturation) or accb overflowed into guard bits and saturated (bit 39 overflow and saturation) 5. oab: logical or of oa and ob 6. sab: logical or of sa and sb the oa and ob bits are modified each time data passes through the adder/subtracter. when set, they indicate that the most recent operation has overflowed into the accumulator guard bits (bits 32 through 39). the oa and ob bits can also optionally generate an arithmetic warning trap when set and the correspond- ing overflow trap flag enable bit (ovate, ovbte) in the intcon1 register (refer to section 5.0 ?inter- rupts? ) is set. this allows the user to take immediate action, for example, to correct system gain.
dspic30f6011/6012/6013/6014 ds70117f-page 22 ? 2006 microchip technology inc. the sa and sb bits are modified each time data passes through the adder/subtracter but can only be cleared by the user. when set, they indicate that the accumulator has overflowed its maximum range (bit 31 for 32-bit saturation, or bit 39 for 40-bit saturation) and will be saturated (if saturation is enabled). when satu- ration is not enabled, sa and sb default to bit 39 over- flow and thus indicate that a catastrophic overflow has occurred. if the covte bit in the intcon1 register is set, sa and sb bits will generate an arithmetic warning trap when saturation is disabled. the overflow and saturation status bits can optionally be viewed in the status register (sr) as the logical or of oa and ob (in bit oab) and the logical or of sa and sb (in bit sab). this allows programmers to check one bit in the status register to determine if either accumulator has overflowed, or one bit to determine if either accumulator has saturated. this would be useful for complex number arithmetic which typically uses both the accumulators. the device supports three saturation and overflow modes: 1. bit 39 overflow and saturation: when bit 39 overflow and saturation occurs, the saturation logic loads the maximally positive 9.31 (0x7fffffffff), or maximally negative 9.31 value (0x8000000000) into the target accumula- tor. the sa or sb bit is set and remains set until cleared by the user. this is referred to as ?super saturation? and provides protection against erro- neous data, or unexpected algorithm problems (e.g., gain calculations). 2. bit 31 overflow and saturation: when bit 31 overflow and saturation occurs, the saturation logic then loads the maximally posi- tive 1.31 value (0x007fffffff), or maximally negative 1.31 value (0x0080000000) into the target accumulator. the sa or sb bit is set and remains set until cleared by the user. when this saturation mode is in effect, the guard bits are not used (so the oa, ob or oab bits are never set). 3. bit 39 catastrophic overflow: the bit 39 overflow status bit from the adder is used to set the sa or sb bit which remain set until cleared by the user. no saturation opera- tion is performed and the accumulator is allowed to overflow (destroying its sign). if the covte bit in the intcon1 register is set, a catastrophic overflow can initiate a trap exception. 2.4.2.2 accumulator ?write back? the mac class of instructions (with the exception of mpy, mpy.n, ed and edac ) can optionally write a rounded version of the high word (bits 31 through 16) of the accumulator that is not targeted by the instruction into data space memory. the write is performed across the x bus into combined x and y address space. the following addressing modes are supported: 1. w13, register direct: the rounded contents of the non-target accumulator are written into w13 as a 1.15 fraction. 2. [w13] + = 2, register indirect with post-increment: the rounded contents of the non-target accumu- lator are written into the address pointed to by w13 as a 1.15 fraction. w13 is then incremented by 2 (for a word write). 2.4.2.3 round logic the round logic is a combinational block which per- forms a conventional (biased) or convergent (unbi- ased) round function during an accumulator write (store). the round mode is determined by the state of the rnd bit in the corcon register. it generates a 16- bit, 1.15 data value which is passed to the data space write saturation logic. if rounding is not indicated by the instruction, a truncated 1.15 data value is stored and the least significant word (lsw) is simply discarded. conventional rounding takes bit 15 of the accumulator, zero-extends it and adds it to the accxh word (bits 16 through 31 of the accumulator). if the accxl word (bits 0 through 15 of the accumulator) is between 0x8000 and 0xffff (0x8000 included), accxh is incremented. if accxl is between 0x0000 and 0x7fff, accxh is left unchanged. a consequence of this algorithm is that over a succession of random rounding operations, the value will tend to be biased slightly positive. convergent (or unbiased) rounding operates in the same manner as conventional rounding, except when accxl equals 0x8000. if this is the case, the lsb (bit 16 of the accumulator) of accxh is examined. if it is ? 1 ?, accxh is incremented. if it is ? 0 ?, accxh is not modified. assuming that bit 16 is effectively random in nature, this scheme will remove any rounding bias that may accumulate. the sac and sac.r instructions store either a trun- cated ( sac ) or rounded ( sac.r ) version of the contents of the target accumulator to data memory via the x bus (subject to data saturation, see section 2.4.2.4 ?data space write saturation? ). note that for the mac class of instructions, the accumulator write back operation will function in the same manner, addressing combined mcu (x and y) data space though the x bus. for this class of instructions, the data is always subject to rounding.
? 2006 microchip technology inc. ds70117f-page 23 dspic30f6011/6012/6013/6014 2.4.2.4 data space write saturation in addition to adder/subtracter saturation, writes to data space may also be saturated but without affecting the contents of the source accumulator. the data space write saturation logic block accepts a 16-bit, 1.15 frac- tional value from the round logic block as its input, together with overflow status from the original source (accumulator) and the 16-bit round adder. these are combined and used to select the appropriate 1.15 fractional value as output to write to data space memory. if the satdw bit in the corcon register is set, data (after rounding or truncation) is tested for overflow and adjusted accordingly, for input data greater than 0x007fff, data written to memory is forced to the max- imum positive 1.15 value, 0x7fff. for input data less than 0xff8000, data written to memory is forced to the maximum negative 1.15 value, 0x8000. the msb of the source (bit 39) is used to determine the sign of the operand being tested. if the satdw bit in the corcon register is not set, the input data is always passed through unmodified under all conditions. 2.4.3 barrel shifter the barrel shifter is capable of performing up to 16-bit arithmetic or logic right shifts, or up to 16-bit left shifts in a single cycle. the source can be either of the two dsp accumulators, or the x bus (to support multi-bit shifts of register or memory data). the shifter requires a signed binary value to determine both the magnitude (number of bits) and direction of the shift operation. a positive value will shift the operand right. a negative value will shift the operand left. a value of ? 0 ? will not modify the operand. the barrel shifter is 40 bits wide, thereby obtaining a 40-bit result for dsp shift operations and a 16-bit result for mcu shift operations. data from the x bus is pre- sented to the barrel shifter between bit positions 16 to 31 for right shifts, and bit positions 0 to 16 for left shifts.
dspic30f6011/6012/6013/6014 ds70117f-page 24 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 25 dspic30f6011/6012/6013/6014 3.0 memory organization 3.1 program address space the program address space is 4m instruction words. it is addressable by a 24-bit value from either the 23-bit pc, table instruction effective address (ea), or data space ea, when program space is mapped into data space as defined by table 3-1. note that the program space address is incremented by two between succes- sive program words in order to provide compatibility with data space addressing. user program space access is restricted to the lower 4m instruction word address range (0x000000 to 0x7ffffe) for all accesses other than tblrd/tblwt , which use tblpag<7> to determine user or configura- tion space access. in table 3-1, program space address construction, bit 23 allows access to the device id, the user id and the configuration bits. otherwise, bit 23 is always clear. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157). note: the address map shown in figure 3-1 and figure 3-2 is conceptual, and the actual memory configuration may vary across individual devices depending on available memory.
dspic30f6011/6012/6013/6014 ds70117f-page 26 ? 2006 microchip technology inc. figure 3-1: program space memory map for dspic30f6011/6013 figure 3-2: program space memory map for dspic30f6012/6014 reset - target address user memory space 000000 00007e 000002 000080 device configuration user flash program memory 016000 015ffe configuration memory space data eeprom (44k instructions) (2 kbytes) 800000 f80000 registers f8000e f80010 devid (2) fefffe ff0000 fffffe reserved f7fffe reserved 7ff800 7ff7fe (read ? 0 ?s) 8005fe 800600 unitid (32 instr.) vector tables 8005be 8005c0 reset - goto instruction 000004 reserved 7ffffe reserved 000100 0000fe 000084 alternate vector table reserved interrupt vector table reset - target address user memory space 000000 00007e 000002 000080 device configuration user flash program memory 018000 017ffe configuration memory space data eeprom (48k instructions) (4 kbytes) 800000 f80000 registers f8000e f80010 devid (2) fefffe ff0000 fffffe reserved f7fffe reserved 7ff000 7feffe (read ? 0 ?s) 8005fe 800600 unitid (32 instr.) vector tables 8005be 8005c0 reset - goto instruction 000004 reserved 7ffffe reserved 000100 0000fe 000084 alternate vector table reserved interrupt vector table
? 2006 microchip technology inc. ds70117f-page 27 dspic30f6011/6012/6013/6014 table 3-1: program space address construction figure 3-3: data access from program space address generation access type access space program space address <23> <22:16> <15> <14:1> <0> instruction access user 0 pc<22:1> 0 tblrd/tblwt user (tblpag<7> = 0 ) tblpag<7:0> data ea<15:0> tblrd/tblwt configuration (tblpag<7> = 1 ) tblpag<7:0> data ea<15:0> program space visibility user 0 psvpag<7:0> data ea<14:0> 0 program counter 23 bits 1 psvpag reg 8 bits ea 15 bits program using select tblpag reg 8 bits ea 16 bits using byte 24-bit ea 0 0 1/0 select user/ configuration table instruction program space counter using space select visibility note: program space visibility cannot be used to access bits <23:16> of a word in program memory.
dspic30f6011/6012/6013/6014 ds70117f-page 28 ? 2006 microchip technology inc. 3.1.1 data access from program memory using table instructions this architecture fetches 24-bit wide program memory. consequently, instructions are always aligned. however, as the architecture is modified harvard, data can also be present in program space. there are two methods by which program space can be accessed: via special table instructions, or through the remapping of a 16k word program space page into the upper half of data space (see section 3.1.2 ?data access from program memory using program space visibility? ). the tblrdl and tblwtl instruc- tions offer a direct method of reading or writing the least significant word of any address within program space, without going through data space. the tblrdh and tblwth instructions are the only method whereby the upper 8 bits of a program space word can be accessed as data. the pc is incremented by two for each successive 24-bit program word. this allows program memory addresses to directly map to data space addresses. program memory can thus be regarded as two 16-bit word wide address spaces, residing side by side, each with the same address range. tblrdl and tblwtl access the space which contains the least significant data word, and tblrdh and tblwth access the space which contains the most significant data byte. figure 3-3 shows how the ea is created for table oper- ations and data space accesses (psv = 1 ). here, p<23:0> refers to a program space word, whereas d<15:0> refers to a data space word. a set of table instructions are provided to move byte or word sized data to and from program space. 1. tblrdl: table read low word: read the lsw of the program address; p<15:0> maps to d<15:0>. byte: read one of the lsbs of the program address; p<7:0> maps to the destination byte when byte select = 0 ; p<15:8> maps to the destination byte when byte select = 1 . 2. tblwtl: table write low (refer to section 6.0 ?flash program memory? for details on flash programming) 3. tblrdh: table read high word: read the most significant word of the pro- gram address; p<23:16> maps to d<7:0>; d<15:8> will always be = 0 . byte: read one of the msbs of the program address; p<23:16> maps to the destination byte when byte select = 0 ; the destination byte will always be = 0 when byte select = 1 . 4. tblwth: table write high (refer to section 6.0 ?flash program memory? for details on flash programming) figure 3-4: program data table access (least significant word) 0 8 16 pc address 0x000000 0x000002 0x000004 0x000006 23 00000000 00000000 00000000 00000000 program memory ?phantom? byte (read as ? 0 ?) tblrdl.w tblrdl.b (wn<0> = 1) tblrdl.b (wn<0> = 0)
? 2006 microchip technology inc. ds70117f-page 29 dspic30f6011/6012/6013/6014 figure 3-5: program data table access (most significant byte) 3.1.2 data access from program memory using program space visibility the upper 32 kbytes of data space may optionally be mapped into any 16k word program space page. this provides transparent access of stored constant data from x data space without the need to use special instructions (i.e., tblrdl/h , tblwtl/h instructions). program space access through the data space occurs if the msb of the data space ea is set and program space visibility is enabled by setting the psv bit in the core control register (corcon). the functions of corcon are discussed in section 2.4 ?dsp engine? . data accesses to this area add an additional cycle to the instruction being executed, since two program memory fetches are required. note that the upper half of addressable data space is always part of the x data space. therefore, when a dsp operation uses program space mapping to access this memory region, y data space should typically con- tain state (variable) data for dsp operations, whereas x data space should typically contain coefficient (constant) data. although each data space address, 0x8000 and higher, maps directly into a corresponding program memory address (see figure 3-6), only the lower 16 bits of the 24-bit program word are used to contain the data. the upper 8 bits should be programmed to force an illegal instruction to maintain machine robustness. refer to the ? dspic30f/33f programmer?s reference manual? (ds70157) for details on instruction encoding. note that by incrementing the pc by 2 for each program memory word, the least significant 15 bits of data space addresses directly map to the least signif- icant 15 bits in the corresponding program space addresses. the remaining bits are provided by the pro- gram space visibility page register, psvpag<7:0>, as shown in figure 3-6. for instructions that use psv which are executed outside a repeat loop: ? the following instructions will require one instruction cycle in addition to the specified execution time: - mac class of instructions with data operand prefetch - mov instructions - mov.d instructions ? all other instructions will require two instruction cycles in addition to the specified execution time of the instruction. for instructions that use psv which are executed inside a repeat loop: ? the following instances will require two instruction cycles in addition to the specified execution time of the instruction: - execution in the first iteration - execution in the last iteration - execution prior to exiting the loop due to an interrupt - execution upon re-entering the loop after an interrupt is serviced ? any other iteration of the repeat loop will allow the instruction accessing data, using psv, to execute in a single cycle. 0 8 16 pc address 0x000000 0x000002 0x000004 0x000006 23 00000000 00000000 00000000 00000000 program memory ?phantom? byte (read as ? 0 ?) tblrdh.w tblrdh.b (wn<0> = 1) tblrdh.b (wn<0> = 0) note: psv access is temporarily disabled during table reads/writes.
dspic30f6011/6012/6013/6014 ds70117f-page 30 ? 2006 microchip technology inc. figure 3-6: data space window into program space operation 23 15 0 psvpag (1) 15 15 ea<15> = 0 ea<15> = 1 16 data space ea data space program space 8 15 23 0x0000 0x8000 0xffff 0x01 0x000100 0x017fff data read upper half of data space is mapped into program space 0x008000 address concatenation bset corcon,#2 ; psv bit set mov #0x01, w0 ; set psvpag register mov w0, psvpag mov 0x8000, w0 ; access program memory location ; using a data space access note: psvpag is an 8-bit register, containing bits <22:15> of the program space address (i.e., it defines the page in program space to which the upper half of data space is being mapped).
? 2006 microchip technology inc. ds70117f-page 31 dspic30f6011/6012/6013/6014 3.2 data address space the core has two data spaces. the data spaces can be considered either separate (for some dsp instruc- tions), or as one unified linear address range (for mcu instructions). the data spaces are accessed using two address generation units (agus) and separate data paths. 3.2.1 data space memory map the data space memory is split into two blocks, x and y data space. a key element of this architecture is that y space is a subset of x space, and is fully contained within x space. in order to provide an apparent linear addressing space, x and y spaces have contiguous addresses. when executing any instruction other than one of the mac class of instructions, the x block consists of the 64- kbyte data address space (including all y addresses). when executing one of the mac class of instructions, the x block consists of the 64-kbyte data address space excluding the y address block (for data reads only). in other words, all other instructions regard the entire data memory as one composite address space. the mac class instructions extract the y address space from data space and address it using eas sourced from w10 and w11. the remaining x data space is addressed using w8 and w9. both address spaces are concurrently accessed only with the mac class instructions. the data space memory maps are shown in figure 3-8 and figure 3-9. 3.2.2 data spaces the x data space is used by all instructions and sup- ports all addressing modes. there are separate read and write data buses. the x read data bus is the return data path for all instructions that view data space as combined x and y address space. it is also the x address space data path for the dual operand read instructions ( mac class). the x write data bus is the only write path to data space for all instructions. the x data space also supports modulo addressing for all instructions, subject to addressing mode restric- tions. bit-reversed addressing is only supported for writes to x data space. the y data space is used in concert with the x data space by the mac class of instructions ( clr, ed, edac, mac, movsac, mpy, mpy.n and msc ) to provide two concurrent data read paths. no writes occur across the y bus. this class of instructions dedi- cates two w register pointers, w10 and w11, to always address y data space, independent of x data space, whereas w8 and w9 always address x data space. note that during accumulator write back, the data address space is considered a combination of x and y data spaces, so the write occurs across the x bus. consequently, the write can be to any address in the entire data space. the y data space can only be used for the data prefetch operation associated with the mac class of instructions. it also supports modulo addressing for automated circular buffers. of course, all other instruc- tions can access the y data address space through the x data path as part of the composite linear space. the boundary between the x and y data spaces is defined as shown in figure 3-8 and figure 3-8 and is not user programmable. should an ea point to data outside its own assigned address space, or to a loca- tion outside physical memory, an all zero word/byte will be returned. for example, although y address space is visible by all non- mac instructions using any address- ing mode, an attempt by a mac instruction to fetch data from that space using w8 or w9 (x space pointers) will return 0x0000.
dspic30f6011/6012/6013/6014 ds70117f-page 32 ? 2006 microchip technology inc. figure 3-7: data space memory map for dspic30f6011/6013 0x0000 0x07fe 0xfffe lsb address 16 bits lsb msb msb address 0x0001 0x07ff 0xffff 0x8001 0x8000 optionally mapped into program memory 0x1fff 0x1ffe 0x2000 0x2001 0x0801 0x0800 0x1801 0x1800 near data 0x17fe 0x17ff 2 kbyte sfr space 6 kbyte sram space 8 kbyte space sfr space x data ram (x) x data unimplemented (x) y data ram (y)
? 2006 microchip technology inc. ds70117f-page 33 dspic30f6011/6012/6013/6014 figure 3-8: data space memory map for dspic30f6012/6014 0x0000 0x07fe 0x17fe 0xfffe lsb address 16 bits lsb msb msb address 0x0001 0x07ff 0x17ff 0xffff 0x8001 0x8000 optionally mapped into program memory 0x27ff 0x27fe 0x2800 0x2801 0x0801 0x0800 0x1801 0x1800 near data 0x1ffe 0x1fff 2 kbyte sfr space 8 kbyte sram space 8 kbyte space sfr space x data ram (x) x data unimplemented (x) y data ram (y)
dspic30f6011/6012/6013/6014 ds70117f-page 34 ? 2006 microchip technology inc. figure 3-9: data space for mcu and dsp ( mac class) instructions example table 3-2: effect of invalid memory accesses all effective addresses are 16 bits wide and point to bytes within the data space. therefore, the data space address range is 64 kbytes or 32k words. 3.2.3 data space width the core data width is 16 bits. all internal registers are organized as 16-bit wide words. data space memory is organized in byte addressable, 16-bit wide blocks. 3.2.4 data alignment to help maintain backward compatibility with pic ? mcu devices and improve data space memory usage efficiency, the dspic30f instruction set supports both word and byte operations. data is aligned in data mem- ory and registers as words, but all data space eas resolve to bytes. data byte reads will read the complete word which contains the byte, using the lsb of any ea to determine which byte to select. the selected byte is placed onto the lsb of the x data path (no byte accesses are possible from the y data path as the mac class of instruction can only fetch words). that is, data memory and registers are organized as two parallel byte wide entities with shared (word) address decode but separate write lines. data byte writes only write to the corresponding side of the array or register which matches the byte address. as a consequence of this byte accessibility, all effective address calculations (including those generated by the dsp operations which are restricted to word sized data) are internally scaled to step through word aligned memory. for example, the core would recognize that post-modified register indirect addressing mode [ws++] will result in a value of ws + 1 for byte operations and ws + 2 for word operations. sfr space (y space) x space sfr space unused x space x space y space unused unused non- mac class ops (read) mac class ops (read) indirect ea from any w indirect ea from w8, w9 indirect ea from w10, w11 attempted operation data returned ea = an unimplemented address 0x0000 w8 or w9 used to access y data space in a mac instruction 0x0000 w10 or w11 used to access x data space in a mac instruction 0x0000
? 2006 microchip technology inc. ds70117f-page 35 dspic30f6011/6012/6013/6014 all word accesses must be aligned to an even address. misaligned word data fetches are not supported so care must be taken when mixing byte and word opera- tions, or translating from 8-bit mcu code. should a mis- aligned read or write be attempted, an address error trap will be generated. if the error occurred on a read, the instruction underway is completed, whereas if it occurred on a write, the instruction will be executed but the write will not occur. in either case, a trap will then be executed, allowing the system and/or user to exam- ine the machine state prior to execution of the address fault. figure 3-10: data alignment all byte loads into any w register are loaded into the lsb. the msb is not modified. a sign-extend ( se ) instruction is provided to allow users to translate 8-bit signed data to 16-bit signed values. alternatively, for 16-bit unsigned data, users can clear the msb of any w register by executing a zero-extend ( ze ) instruction on the appropriate address. although most instructions are capable of operating on word or byte data sizes, it should be noted that some instructions, including the dsp instructions, operate only on words. 3.2.5 near data space an 8-kbyte ?near? data space is reserved in x address memory space between 0x0000 and 0x1fff, which is directly addressable via a 13-bit absolute address field within all memory direct instructions. the remaining x address space and all of the y address space is addressable indirectly. additionally, the whole of x data space is addressable using mov instructions, which support memory direct addressing with a 16-bit address field. 3.2.6 software stack the dspic dsc devices contain a software stack. w15 is used as the stack pointer. the stack pointer always points to the first available free word and grows from lower addresses towards higher addresses. it pre-decrements for stack pops and post-increments for stack pushes as shown in figure 3- 11. note that for a pc push during any call instruc- tion, the msb of the pc is zero-extended before the push, ensuring that the msb is always clear. there is a stack pointer limit register (splim) associ- ated with the stack pointer. splim is uninitialized at reset. as is the case for the stack pointer, splim<0> is forced to ? 0 ? because all stack operations must be word aligned. whenever an effective address (ea) is generated using w15 as a source or destination pointer, the address thus generated is compared with the value in splim. if the contents of the stack pointer (w15) and the splim register are equal and a push operation is performed, a stack error trap will not occur. the stack error trap will occur on a subsequent push operation. thus, for example, if it is desirable to cause a stack error trap when the stack grows beyond address 0x2000 in ram, initialize the splim with the value, 0x1ffe. similarly, a stack pointer underflow (stack error) trap is generated when the stack pointer address is found to be less than 0x0800, thus preventing the stack from interfering with the special function register (sfr) space. a write to the splim register should not be immediately followed by an indirect read operation using w15. figure 3-11: call stack frame 15 8 7 0 0001 0003 0005 0000 0002 0004 byte1 byte 0 byte3 byte 2 byte5 byte 4 lsb msb note: a pc push during exception processing will concatenate the srl register to the msb of the pc prior to the push. pc<15:0> 000000000 0 15 w15 (before call ) w15 (after call ) stack grows towards higher address 0x0000 pc<22:16> pop : [--w15] push : [w15++]
dspic30f6011/6012/6013/6014 ds70117f-page 36 ? 2006 microchip technology inc. table 3-3: core register map sfr name address (home) bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state w0 0000 w0 / wreg 0000 0000 0000 0000 w1 0002 w1 0000 0000 0000 0000 w2 0004 w2 0000 0000 0000 0000 w3 0006 w3 0000 0000 0000 0000 w4 0008 w4 0000 0000 0000 0000 w5 000a w5 0000 0000 0000 0000 w6 000c w6 0000 0000 0000 0000 w7 000e w7 0000 0000 0000 0000 w8 0010 w8 0000 0000 0000 0000 w9 0012 w9 0000 0000 0000 0000 w10 0014 w10 0000 0000 0000 0000 w11 0016 w11 0000 0000 0000 0000 w12 0018 w12 0000 0000 0000 0000 w13 001a w13 0000 0000 0000 0000 w14 001c w14 0000 0000 0000 0000 w15 001e w15 0000 1000 0000 0000 splim 0020 splim 0000 0000 0000 0000 accal 0022 accal 0000 0000 0000 0000 accah 0024 accah 0000 0000 0000 0000 accau 0026 sign-extension (acca<39>) accau 0000 0000 0000 0000 accbl 0028 accbl 0000 0000 0000 0000 accbh 002a accbh 0000 0000 0000 0000 accbu 002c sign-extension (accb<39>) accbu 0000 0000 0000 0000 pcl 002e pcl 0000 0000 0000 0000 pch 0030 ? ? ? ? ? ? ? ? ?pch 0000 0000 0000 0000 tblpag 0032 ? ? ? ? ? ? ? ?tblpag 0000 0000 0000 0000 psvpag 0034 ? ? ? ? ? ? ? ? psvpag 0000 0000 0000 0000 rcount 0036 rcount uuuu uuuu uuuu uuuu dcount 0038 dcount uuuu uuuu uuuu uuuu dostartl 003a dostartl 0 uuuu uuuu uuuu uuu0 dostarth 003c ? ? ? ? ? ? ? ? ?dostarth 0000 0000 0uuu uuuu doendl 003e doendl 0 uuuu uuuu uuuu uuu0 doendh 0040 ? ? ? ? ? ? ? ? ? doendh 0000 0000 0uuu uuuu legend: u = uninitialized bit note: refer to ? dspic30f family reference manual ? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 37 dspic30f6011/6012/6013/6014 sr 0042 oa ob sa sb oab sab da dc ipl2 ipl1 ipl0 ra n ov z c 0000 0000 0000 0000 corcon 0044 ? ? ? us edt dl2 dl1 dl0 sata satb satdw accsat ipl3 psv rnd if 0000 0000 0010 0000 modcon 0046 xmoden ymoden ? ? bwm<3:0> ywm<3:0> xwm<3:0> 0000 0000 0000 0000 xmodsrt 0048 xs<15:1> 0 uuuu uuuu uuuu uuu0 xmodend 004a xe<15:1> 1 uuuu uuuu uuuu uuu1 ymodsrt 004c ys<15:1> 0 uuuu uuuu uuuu uuu0 ymodend 004e ye<15:1> 1 uuuu uuuu uuuu uuu1 xbrev 0050 bren xb<14:0> uuuu uuuu uuuu uuuu disicnt 0052 ? ? disicnt<13:0> 0000 0000 0000 0000 table 3-3: core register map (continued) sfr name address (home) bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state legend: u = uninitialized bit note: refer to ? dspic30f family reference manual ? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 38 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 39 dspic30f6011/6012/6013/6014 4.0 address generator units the dspic dsc core contains two independent address generator units: the x agu and y agu. the y agu supports word-sized data reads for the dsp mac class of instructions only. the dspic30f agus support: ? linear addressing ? modulo (circular) addressing ? bit-reversed addressing linear and modulo data addressing modes can be applied to data space or program space. bit-reversed addressing is only applicable to data space addresses. 4.1 instruction addressing modes the addressing modes in table 4-1 form the basis of the addressing modes optimized to support the specific features of individual instructions. the addressing modes provided in the mac class of instructions are somewhat different from those in the other instruction types. 4.1.1 file register instructions most file register instructions use a 13-bit address field (f) to directly address data present in the first 8192 bytes of data memory (near data space). most file register instructions employ a working register, w0, which is denoted as wreg in these instructions. the destination is typically either the same file register or wreg (with the exception of the mul instruction), which writes the result to a register or register pair. the mov instruction allows additional flexibility and can access the entire data space. 4.1.2 mcu instructions the three-operand mcu instructions are of the form: operand 3 = operand 1 operand 2 where operand 1 is always a working register (i.e., the addressing mode can only be register direct) which is referred to as wb. operand 2 can be a w register, fetched from data memory or a 5-bit literal. the result location can be either a w register or a data memory location. the following addressing modes are supported by mcu instructions: ? register direct ? register indirect ? register indirect post-modified ? register indirect pre-modified ? 5-bit or 10-bit literal table 4-1: fundamental addressing modes supported note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157). note: not all instructions support all the address- ing modes given above. individual instruc- tions may support different subsets of these addressing modes. addressing mode description file register direct the address of the file register is specified explicitly. register direct the contents of a register are accessed directly. register indirect the contents of wn forms the ea. register indirect post-modified the contents of wn forms the ea. wn is post-modified (incremented or decremented) by a constant value. register indirect pre-modified wn is pre-modified (incremented or decremented) by a signed constant value to form the ea. register indirect with register offset the sum of wn and wb forms the ea. register indirect with literal offset the sum of wn and a literal forms the ea.
dspic30f6011/6012/6013/6014 ds70117f-page 40 ? 2006 microchip technology inc. 4.1.3 move and accumulator instructions move instructions and the dsp accumulator class of instructions provide a greater degree of addressing flexibility than other instructions. in addition to the addressing modes supported by most mcu instruc- tions, move and accumulator instructions also support register indirect with register offset addressing mode, also referred to as register indexed mode. in summary, the following addressing modes are supported by move and accumulator instructions: ? register direct ? register indirect ? register indirect post-modified ? register indirect pre-modified ? register indirect with register offset (indexed) ? register indirect with literal offset ? 8-bit literal ? 16-bit literal 4.1.4 mac instructions the dual source operand dsp instructions ( clr, ed, edac, mac, mpy, mpy.n, movsac and msc ), also referred to as mac instructions, utilize a simplified set of addressing modes to allow the user to effectively manipulate the data pointers through register indirect tables. the 2 source operand prefetch registers must be a member of the set {w8, w9, w10, w11}. for data reads, w8 and w9 will always be directed to the x ragu and w10 and w11 will always be directed to the y agu. the effective addresses generated (before and after modification) must, therefore, be valid addresses within x data space for w8 and w9 and y data space for w10 and w11. in summary, the following addressing modes are supported by the mac class of instructions: ? register indirect ? register indirect post-modified by 2 ? register indirect post-modified by 4 ? register indirect post-modified by 6 ? register indirect with register offset (indexed) 4.1.5 other instructions besides the various addressing modes outlined above, some instructions use literal constants of various sizes. for example, bra (branch) instructions use 16-bit signed literals to specify the branch destination directly, whereas the disi instruction uses a 14-bit unsigned literal field. in some instructions, such as add acc , the source of an operand or result is implied by the opcode itself. certain operations, such as nop , do not have any operands. 4.2 modulo addressing modulo addressing is a method of providing an auto- mated means to support circular data buffers using hardware. the objective is to remove the need for soft- ware to perform data address boundary checks when executing tightly looped code, as is typical in many dsp algorithms. modulo addressing can operate in either data or pro- gram space (since the data pointer mechanism is essentially the same for both). one circular buffer can be supported in each of the x (which also provides the pointers into program space) and y data spaces. mod- ulo addressing can operate on any w register pointer. however, it is not advisable to use w14 or w15 for mod- ulo addressing since these two registers are used as the stack frame pointer and stack pointer, respectively. in general, any particular circular buffer can only be configured to operate in one direction, as there are cer- tain restrictions on the buffer start address (for incre- menting buffers), or end address (for decrementing buffers) based upon the direction of the buffer. the only exception to the usage restrictions is for buff- ers which have a power-of-2 length. as these buffers satisfy the start and end address criteria, they may operate in a bidirectional mode (i.e., address boundary checks will be performed on both the lower and upper address boundaries). note: for the mov instructions, the addressing mode specified in the instruction can differ for the source and destination ea. however, the 4-bit wb (register offset) field is shared between both source and destination (but typically only used by one). note: not all instructions support all the address- ing modes given above. individual instruc- tions may support different subsets of these addressing modes. note: register indirect with register offset addressing is only available for w9 (in x space) and w11 (in y space).
? 2006 microchip technology inc. ds70117f-page 41 dspic30f6011/6012/6013/6014 4.2.1 start and end address the modulo addressing scheme requires that a start- ing and an ending address be specified and loaded into the 16-bit modulo buffer address registers: xmodsrt, xmodend, ymodsrt, ymodend (see table 3-3). the length of a circular buffer is not directly specified. it is determined by the difference between the corre- sponding start and end addresses. the maximum possible length of the circular buffer is 32k words (64 kbytes). 4.2.2 w address register selection the modulo and bit-reversed addressing control reg- ister modcon<15:0> contains enable flags as well as a w register field to specify the w address registers. the xwm and ywm fields select which registers will operate with modulo addressing. if xwm = 15 , x ragu and x wagu modulo addressing is disabled. similarly, if ywm = 15 , y agu modulo addressing is disabled. the x address space pointer w register (xwm), to which modulo addressing is to be applied, is stored in modcon<3:0> (see table 3-3). modulo addressing is enabled for x data space when xwm is set to any value other than ? 15 ? and the xmoden bit is set at modcon<15>. the y address space pointer w register (ywm), to which modulo addressing is to be applied, is stored in modcon<7:4>. modulo addressing is enabled for y data space when ywm is set to any value other than ? 15 ? and the ymoden bit is set at modcon<14>. figure 4-1: modulo addressing operation example note: y space modulo addressing ea calcula- tions assume word sized data (lsb of every ea is always clear). 0x1100 0x1163 start addr = 0x1100 end addr = 0x1163 length = 0x0032 words byte address mov #0x1100,w0 mov w0,xmodsrt ;set modulo start address mov #0x1163,w0 mov w0,modend ;set modulo end address mov #0x8001,w0 mov w0,modcon ;enable w1, x agu for modulo mov #0x0000,w0 ;w0 holds buffer fill value mov #0x1110,w1 ;point w1 to buffer do again,#0x31 ;fill the 50 buffer locations mov w0,[w1++] ;fill the next location
dspic30f6011/6012/6013/6014 ds70117f-page 42 ? 2006 microchip technology inc. 4.2.3 modulo addressing applicability modulo addressing can be applied to the effective address calculation associated with any w register. it is important to realize that the address boundaries check for addresses less than, or greater than the upper (for incrementing buffers), and lower (for decrementing buffers) boundary addresses (not just equal to). address changes may, therefore, jump beyond bound- aries and still be adjusted correctly. 4.3 bit-reversed addressing bit-reversed addressing is intended to simplify data re-ordering for radix-2 fft algorithms. it is supported by the x agu for data writes only. the modifier, which may be a constant value or register contents, is regarded as having its bit order reversed. the address source and destination are kept in normal order. thus, the only operand requiring reversal is the modifier. 4.3.1 bit-reversed addressing implementation bit-reversed addressing is enabled when: 1. bwm (w register selection) in the modcon register is any value other than ? 15 ? (the stack cannot be accessed using bit-reversed addressing) and 2. the bren bit is set in the xbrev register and 3. the addressing mode used is register indirect with pre-increment or post-increment. if the length of a bit-reversed buffer is m = 2 n bytes, then the last ?n? bits of the data buffer start address must be zeros. xb<14:0> is the bit-reversed address modifier or ?pivot point? which is typically a constant. in the case of an fft computation, its value is equal to half of the fft data buffer size. when enabled, bit-reversed addressing will only be executed for register indirect with pre-increment or post-increment addressing and word sized data writes. it will not function for any other addressing mode or for byte sized data, and normal addresses will be gener- ated instead. when bit-reversed addressing is active, the w address pointer will always be added to the address modifier (xb) and the offset associated with the register indirect addressing mode will be ignored. in addition, as word sized data is a requirement, the lsb of the ea is ignored (and always clear). if bit-reversed addressing has already been enabled by setting the bren (xbrev<15>) bit, then a write to the xbrev register should not be immediately followed by an indirect read operation using the w register that has been designated as the bit-reversed pointer. note: the modulo corrected effective address is written back to the register only when pre- modify or post-modify addressing mode is used to compute the effective address. when an address offset (e.g., [w7 + w2]) is used, modulo address correction is per- formed but the contents of the register remain unchanged. note: all bit-reversed ea calculations assume word sized data (lsb of every ea is always clear). the xb value is scaled accordingly to generate compatible (byte) addresses. note: modulo addressing and bit-reversed addressing should not be enabled together. in the event that the user attempts to do this, bit-reversed addressing will assume priority when active for the x wagu, and x wagu modulo addressing will be disabled. however, modulo addressing will continue to function in the x ragu.
? 2006 microchip technology inc. ds70117f-page 43 dspic30f6011/6012/6013/6014 figure 4-2: bit-reversed address example table 4-2: bit-reversed address sequence (16-entry) table 4-3: bit-reversed address modifier values for xbrev register normal address bit-reversed address a3 a2 a1 a0 decimal a3 a2 a1 a0 decimal 0000 0 0000 0 0001 1 1000 8 0010 2 0100 4 0011 3 1100 12 0100 4 0010 2 0101 5 1010 10 0110 6 0110 6 0111 7 1110 14 1000 8 0001 1 1001 9 1001 9 1010 10 0101 5 1011 11 1101 13 1100 12 0011 3 1101 13 1011 11 1110 14 0111 7 1111 15 1111 15 buffer size (words) xb<14:0> bit-reversed address modifier value 4096 0x0800 2048 0x0400 1024 0x0200 512 0x0100 256 0x0080 128 0x0040 64 0x0020 32 0x0010 16 0x0008 8 0x0004 4 0x0002 2 0x0001 b3 b2 b1 0 b2 b3 b4 0 bit locations swapped left-to-right around center of binary value bit-reversed address xb = 0x0008 for a 16-word bit-reversed buffer b7 b6 b5 b1 b7 b6 b5 b4 b11 b10 b9 b8 b11 b10 b9 b8 b15 b14 b13 b12 b15 b14 b13 b12 sequential address pivot point
dspic30f6011/6012/6013/6014 ds70117f-page 44 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 45 dspic30f6011/6012/6013/6014 5.0 interrupts the dspic30f sensor and general purpose family has up to 41 interrupt sources and 4 processor excep- tions (traps) which must be arbitrated based on a priority scheme. the cpu is responsible for reading the interrupt vector table (ivt) and transferring the address contained in the interrupt vector to the program counter. the inter- rupt vector is transferred from the program data bus into the program counter via a 24-bit wide multiplexer on the input of the program counter. the interrupt vector table (ivt) and alternate interrupt vector table (aivt) are placed near the beginning of program memory (0x000004). the ivt and aivt are shown in table 5-1. the interrupt controller is responsible for pre- processing the interrupts and processor exceptions prior to them being presented to the processor core. the peripheral interrupts and traps are enabled, priori- tized and controlled using centralized special function registers: ? ifs0<15:0>, ifs1<15:0>, ifs2<15:0> all interrupt request flags are maintained in these three registers. the flags are set by their respec- tive peripherals or external signals, and they are cleared via software. ? iec0<15:0>, iec1<15:0>, iec2<15:0> all interrupt enable control bits are maintained in these three registers. these control bits are used to individually enable interrupts from the peripherals or external signals. ? ipc0<15:0>... ipc10<7:0> the user assignable priority level associated with each of these 41 interrupts is held centrally in these twelve registers. ? ipl<3:0> the current cpu priority level is explicitly stored in the ipl bits. ipl<3> is present in the corcon register, whereas ipl<2:0> are present in the status register (sr) in the processor core. ? intcon1<15:0>, intcon2<15:0> global interrupt control functions are derived from these two registers. intcon1 contains the con- trol and status flags for the processor exceptions. the intcon2 register controls the external interrupt request signal behavior and the use of the alternate vector table. all interrupt sources can be user assigned to one of 7 priority levels, 1 through 7, via the ipcx registers. each interrupt source is associated with an interrupt vector, as shown in table 5-1. levels 7 and 1 represent the highest and lowest maskable priorities, respectively. if the nstdis bit (intcon1<15>) is set, nesting of interrupts is prevented. thus, if an interrupt is currently being serviced, processing of a new interrupt is pre- vented even if the new interrupt is of higher priority than the one currently being serviced. certain interrupts have specialized control bits for fea- tures like edge or level triggered interrupts, interrupt- on-change, etc. control of these features remains within the peripheral module which generates the interrupt. the disi instruction can be used to disable the pro- cessing of interrupts of priorities 6 and lower for a cer- tain number of instructions, during which the disi bit (intcon2<14>) remains set. when an interrupt is serviced, the pc is loaded with the address stored in the vector location in program mem- ory that corresponds to the interrupt. there are 63 dif- ferent vectors within the ivt (refer to table 5-1). these vectors are contained in locations 0x000004 through 0x0000fe of program memory (refer to table 5-1). these locations contain 24-bit addresses and in order to preserve robustness, an address error trap will take place should the pc attempt to fetch any of these words during normal execution. this prevents execu- tion of random data as a result of accidentally decre- menting a pc into vector space, accidentally mapping a data space address into vector space, or the pc roll- ing over to 0x000000 after reaching the end of imple- mented program memory space. execution of a goto instruction to this vector space will also generate an address error trap. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157). note: interrupt flag bits get set when an interrupt condition occurs, regardless of the state of its corresponding enable bit. user soft- ware should ensure the appropriate inter- rupt flag bits are clear prior to enabling an interrupt. note: assigning a priority level of ? 0 ? to an inter- rupt source is equivalent to disabling that interrupt. note: the ipl bits become read only whenever the nstdis bit has been set to ? 1 ?.
dspic30f6011/6012/6013/6014 ds70117f-page 46 ? 2006 microchip technology inc. 5.1 interrupt priority the user assignable interrupt priority (ip<2:0>) bits for each individual interrupt source are located in the least significant 3 bits of each nibble within the ipcx regis- ter(s). bit 3 of each nibble is not used and is read as a ? 0 ?. these bits define the priority level assigned to a particular interrupt by the user. natural order priority is determined by the position of an interrupt in the vector table, and only affects interrupt operation when multiple interrupts with the same user-assigned priority become pending at the same time. table 5-1 lists the interrupt numbers and interrupt sources for the dspic dsc device and their associated vector numbers. the ability for the user to assign every interrupt to one of seven priority levels implies that the user can assign a very high overall priority level to an interrupt with a low natural order priority. for example, the plvd (low- voltage detect) can be given a priority of 7. the int0 (external interrupt 0) may be assigned to priority level 1, thus giving it a very low effective priority. table 5-1: interrupt vector table note: the user selectable priority levels start at 0 as the lowest priority and level 7 as the highest priority. note 1: the natural order priority scheme has 0 as the highest priority and 53 as the lowest priority. 2: the natural order priority number is the same as the int number. int number vector number interrupt source highest natural order priority 0 8 int0 ? external interrupt 0 1 9 ic1 ? input capture 1 2 10 oc1 ? output compare 1 3 11 t1 ? timer 1 4 12 ic2 ? input capture 2 5 13 oc2 ? output compare 2 6 14 t2 ? timer 2 7 15 t3 ? timer 3 816spi1 9 17 u1rx ? uart1 receiver 10 18 u1tx ? uart1 transmitter 11 19 adc ? adc convert done 12 20 nvm ? nvm write complete 13 21 si2c ? i 2 c slave interrupt 14 22 mi2c ? i 2 c master interrupt 15 23 input change interrupt 16 24 int1 ? external interrupt 1 17 25 ic7 ? input capture 7 18 26 ic8 ? input capture 8 19 27 oc3 ? output compare 3 20 28 oc4 ? output compare 4 21 29 t4 ? timer 4 22 30 t5 ? timer 5 23 31 int2 ? external interrupt 2 24 32 u2rx ? uart2 receiver 25 33 u2tx ? uart2 transmitter 26 34 spi2 27 35 c1 ? combined irq for can1 28 36 ic3 ? input capture 3 29 37 ic4 ? input capture 4 30 38 ic5 ? input capture 5 31 39 ic6 ? input capture 6 32 40 oc5 ? output compare 5 33 41 oc6 ? output compare 6 34 42 oc7 ? output compare 7 35 43 oc8 ? output compare 8 36 44 int3 ? external interrupt 3 37 45 int4 ? external interrupt 4 38 46 c2 ? combined irq for can2 39-40 47-48 reserved 41 49 dci ? codec transfer done 42 50 lvd ? low-voltage detect 43-53 51-61 reserved lowest natural order priority
? 2006 microchip technology inc. ds70117f-page 47 dspic30f6011/6012/6013/6014 5.2 reset sequence a reset is not a true exception, because the interrupt controller is not involved in the reset process. the pro- cessor initializes its registers in response to a reset which forces the pc to zero. the processor then begins program execution at location 0x000000. a goto instruction is stored in the first program memory loca- tion immediately followed by the address target for the goto instruction. the processor executes the goto to the specified address and then begins operation at the specified target (start) address. 5.2.1 reset sources in addition to external reset and power-on reset (por), there are 6 sources of error conditions which ?trap? to the reset vector. ? watchdog time-out: the watchdog has timed out, indicating that the processor is no longer executing the correct flow of code. ? uninitialized w register trap: an attempt to use an uninitialized w register as an address pointer will cause a reset. ? illegal instruction trap: attempted execution of any unused opcodes will result in an illegal instruction trap. note that a fetch of an illegal instruction does not result in an illegal instruction trap if that instruction is flushed prior to execution due to a flow change. ? brown-out reset (bor): a momentary dip in the power supply to the device has been detected which may result in malfunction. ? trap lockout: occurrence of multiple trap conditions simultaneously will cause a reset. 5.3 traps traps can be considered as non-maskable interrupts indicating a software or hardware error, which adhere to a predefined priority, as shown in table 5-1. they are intended to provide the user a means to correct erroneous operation during debug and when operating within the application. note that many of these trap conditions can only be detected when they occur. consequently, the question- able instruction is allowed to complete prior to trap exception processing. if the user chooses to recover from the error, the result of the erroneous action that caused the trap may have to be corrected. there are 8 fixed priority levels for traps: level 8 through level 15, which implies that the ipl3 is always set during processing of a trap. if the user is not currently executing a trap, and he sets the ipl<3:0> bits to a value of ? 0111 ? (level 7), then all interrupts are disabled but traps can still be processed. 5.3.1 trap sources the following traps are provided with increasing prior- ity. however, since all traps can be nested, priority has little effect. math error trap: the math error trap executes under the following four circumstances: 1. should an attempt be made to divide by zero, the divide operation will be aborted on a cycle boundary and the trap taken. 2. if enabled, a math error trap will be taken when an arithmetic operation on either accumulator a or b causes an overflow from bit 31 and the accumulator guard bits are not utilized. 3. if enabled, a math error trap will be taken when an arithmetic operation on either accumulator a or b causes a catastrophic overflow from bit 39 and all saturation is disabled. 4. if the shift amount specified in a shift instruction is greater than the maximum allowed shift amount, a trap will occur. address error trap: this trap is initiated when any of the following circumstances occurs: 1. a misaligned data word access is attempted. 2. a data fetch from and unimplemented data memory location is attempted. 3. a data fetch from an unimplemented program memory location is attempted. 4. an instruction fetch from vector space is attempted. note: if the user does not intend to take correc- tive action in the event of a trap error con- dition, these vectors must be loaded with the address of a default handler that sim- ply contains the reset instruction. if, on the other hand, one of the vectors contain- ing an invalid address is called, an address error trap is generated. note: in the mac class of instructions, wherein the data space is split into x and y data space, unimplemented x space includes all of y space, and unimplemented y space includes all of x space.
dspic30f6011/6012/6013/6014 ds70117f-page 48 ? 2006 microchip technology inc. 5. execution of a ? bra #litera l? instruction or a ? goto #literal ? instruction, where literal is an unimplemented program memory address. 6. executing instructions after modifying the pc to point to unimplemented program memory addresses. the pc may be modified by loading a value into the stack and executing a return instruction. stack error trap: this trap is initiated under the following conditions: 1. the stack pointer is loaded with a value which is greater than the (user programmable) limit value written into the splim register (stack overflow). 2. the stack pointer is loaded with a value which is less than 0x0800 (simple stack underflow). oscillator fail trap: this trap is initiated if the external oscillator fails and operation becomes reliant on an internal rc backup. 5.3.2 hard and soft traps it is possible that multiple traps can become active within the same cycle (e.g., a misaligned word stack write to an overflowed address). in such a case, the fixed priority shown in figure 5-1 is implemented, which may require the user to check if other traps are pending in order to completely correct the fault. ?soft? traps include exceptions of priority level 8 through level 11, inclusive. the arithmetic error trap (level 11) falls into this category of traps. ?hard? traps include exceptions of priority level 12 through level 15, inclusive. the address error (level 12), stack error (level 13) and oscillator error (level 14) traps fall into this category. each hard trap that occurs must be acknowledged before code execution of any type may continue. if a lower priority hard trap occurs while a higher priority trap is pending, acknowledged, or is being processed, a hard trap conflict will occur. the device is automatically reset in a hard trap conflict condition. the trapr status bit (rcon<15>) is set when the reset occurs so that the condition may be detected in software. figure 5-1: trap vectors 5.4 interrupt sequence all interrupt event flags are sampled in the beginning of each instruction cycle by the ifsx registers. a pending interrupt request (irq) is indicated by the flag bit being equal to a ? 1 ? in an ifsx register. the irq will cause an interrupt to occur if the corresponding bit in the interrupt enable (iecx) register is set. for the remainder of the instruction cycle, the priorities of all pending interrupt requests are evaluated. if there is a pending irq with a priority level greater than the current processor priority level in the ipl bits, the processor will be interrupted. the processor then stacks the current program counter and the low byte of the processor status register (srl), as shown in figure 5-2. the low byte of the status register contains the processor priority level at the time prior to the beginning of the interrupt cycle. the processor then loads the priority level for this inter- rupt into the status register. this action will disable all lower priority interrupts until the completion of the interrupt service routine. address error trap vector oscillator fail trap vector stack error trap vector reserved vector math error trap vector reserved oscillator fail trap vector address error trap vector reserved vector reserved vector interrupt 0 vector interrupt 1 vector ~ ~ ~ interrupt 52 vector interrupt 53 vector math error trap vector decreasing priority 0x000000 0x000014 reserved stack error trap vector reserved vector reserved vector interrupt 0 vector interrupt 1 vector ~ ~ ~ interrupt 52 vector interrupt 53 vector ivt aivt 0x000080 0x00007e 0x0000fe reserved 0x000094 reset - goto instruction reset - goto address 0x000002 reserved 0x000082 0x000084 0x000004 reserved vector
? 2006 microchip technology inc. ds70117f-page 49 dspic30f6011/6012/6013/6014 figure 5-2: interrupt stack frame the retfie (return from interrupt) instruction will unstack the program counter and status registers to return the processor to its state prior to the interrupt sequence. 5.5 alternate vector table in program memory, the interrupt vector table (ivt) is followed by the alternate interrupt vector table (aivt), as shown in table 5-1. access to the alternate vector table is provided by the altivt bit in the intcon2 reg- ister. if the altivt bit is set, all interrupt and exception processes will use the alternate vectors instead of the default vectors. the alternate vectors are organized in the same manner as the default vectors. the aivt sup- ports emulation and debugging efforts by providing a means to switch between an application and a support environment without requiring the interrupt vectors to be reprogrammed. this feature also enables switching between applications for evaluation of different software algorithms at run time. if the aivt is not required, the program memory allo- cated to the aivt may be used for other purposes. aivt is not a protected section and may be freely programmed by the user. 5.6 fast context saving a context saving option is available using shadow reg- isters. shadow registers are provided for the dc, n, ov, z and c bits in sr, and the registers w0 through w3. the shadows are only one level deep. the shadow registers are accessible using the push.s and pop.s instructions only. when the processor vectors to an interrupt, the push.s instruction can be used to store the current value of the aforementioned registers into their respective shadow registers. if an isr of a certain priority uses the push.s and pop.s instructions for fast context saving, then a higher priority isr should not include the same instruc- tions. users must save the key registers in software during a lower priority interrupt if the higher priority isr uses fast context saving. 5.7 external interrupt requests the interrupt controller supports up to five external interrupt request signals, int0-int4. these inputs are edge sensitive; they require a low-to-high or a high-to- low transition to generate an interrupt request. the intcon2 register has five bits, int0ep-int4ep, that select the polarity of the edge detection circuitry. 5.8 wake-up from sleep and idle the interrupt controller may be used to wake-up the processor from either sleep or idle modes, if sleep or idle mode is active when the interrupt is generated. if an enabled interrupt request of sufficient priority is received by the interrupt controller, then the standard interrupt request is presented to the processor. at the same time, the processor will wake-up from sleep or idle and begin execution of the interrupt service routine (isr) needed to process the interrupt request. note 1: the user can always lower the priority level by writing a new value into sr. the interrupt service routine must clear the interrupt flag bits in the ifsx register before lowering the processor interrupt priority, in order to avoid recursive interrupts. 2: the ipl3 bit (corcon<3>) is always clear when interrupts are being pro- cessed. it is set only during execution of traps. 0 15 w15 (before call ) w15 (after call ) stack grows towards higher address 0x0000 pc<15:0> srl ipl3 pc<22:16> pop : [--w15] push: [w15++]
dspic30f6011/6012/6013/6014 ds70117f-page 50 ? 2006 microchip technology inc. table 5-2: interrupt controller register map sfr name adr bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state intcon1 0080 nstdis ? ? ? ? ovate ovbte covte ? ? ? matherr addrerr stkerr oscfail ? 0000 0000 0000 0000 intcon2 0082 altivt disi ? ? ? ? ? ? ? ? ? int4ep int3ep int2ep int1ep int0ep 0000 0000 0000 0000 ifs0 0084 cnif mi2cif si2cif nvmif adif u1txif u1rxif spi1if t3if t2if oc2if ic2if t1if oc1if ic1if int0if 0000 0000 0000 0000 ifs1 0086 ic6if ic5if ic4if ic3if c1if spi2if u2txif u2rxif int2if t5if t4if oc4if oc3if ic8if ic7if int1if 0000 0000 0000 0000 ifs2 0088 ? ? ? ? ? lvdif dciif ? ? c2if int4if int3if oc8if oc7if oc6if oc5if 0000 0000 0000 0000 iec0 008c cnie mi2cie si2cie nvmie adie u1txie u1rxie spi1ie t3ie t2ie oc2ie ic2ie t1ie oc1ie ic1ie int0ie 0000 0000 0000 0000 iec1 008e ic6ie ic5ie ic4ie ic3ie c1ie spi2ie u2txie u2rxie int2ie t5ie t4ie oc4ie oc3ie ic8ie ic7ie int1ie 0000 0000 0000 0000 iec2 0090 ? ? ? ? ? lvdie dciie ? ? c2ie int4ie int3ie oc8ie oc7ie oc6ie oc5ie 0000 0000 0000 0000 ipc0 0094 ? t1ip<2:0> ?oc1ip<2:0> ? ic1ip<2:0> ? int0ip<2:0> 0100 0100 0100 0100 ipc1 0096 ? t31p<2:0> ? t2ip<2:0> ? oc2ip<2:0> ? ic2ip<2:0> 0100 0100 0100 0100 ipc2 0098 ?adip<2:0> ? u1txip<2:0> ? u1rxip<2:0> ? spi1ip<2:0> 0100 0100 0100 0100 ipc3 009a ? cnip<2:0> ?mi2cip<2:0> ? si2cip<2:0> ? nvmip<2:0> 0100 0100 0100 0100 ipc4 009c ?oc3ip<2:0> ?ic8ip<2:0> ? ic7ip<2:0> ? int1ip<2:0> 0100 0100 0100 0100 ipc5 009e ? int2ip<2:0> ? t5ip<2:0> ? t4ip<2:0> ? oc4ip<2:0> 0100 0100 0100 0100 ipc6 00a0 ? c1ip<2:0> ? spi2ip<2:0> ? u2txip<2:0> ? u2rxip<2:0> 0100 0100 0100 0100 ipc7 00a2 ? ic6ip<2:0> ?ic5ip<2:0> ? ic4ip<2:0> ? ic3ip<2:0> 0100 0100 0100 0100 ipc8 00a4 ?oc8ip<2:0> ?oc7ip<2:0> ? oc6ip<2:0> ? oc5ip<2:0> 0100 0100 0100 0100 ipc9 00a6 ? ? ? ? ? c2ip<2:0> ? int41ip<2:0> ? int3ip<2:0> 0000 0100 0100 0100 ipc10 00a8 ? ? ? ? ? lvdip<2:0> ? dciip<2:0> ? ? ? ? 0000 0100 0100 0000 legend: u = uninitialized bit note: refer to ? dspic30f family reference manual ? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 51 dspic30f6011/6012/6013/6014 6.0 flash program memory the dspic30f family of devices contains internal pro- gram flash memory for executing user code. there are two methods by which the user can program this memory: 1. run-time self-programming (rtsp) 2. in-circuit serial programming (icsp) 6.1 in-circuit serial programming (icsp) dspic30f devices can be serially programmed while in the end application circuit. this is simply done with two lines for programming clock and programming data (which are named pgc and pgd respectively), and three other lines for power (v dd ), ground (v ss ) and master clear (mclr ). this allows customers to manu- facture boards with unprogrammed devices, and then program the microcontroller just before shipping the product. this also allows the most recent firmware or a custom firmware to be programmed. 6.2 run-time self-programming (rtsp) rtsp is accomplished using tblrd (table read) and tblwt (table write) instructions. with rtsp, the user may erase program memory, 32 instructions (96 bytes) at a time and can write program memory data, 32 instructions (96 bytes) at a time. 6.3 table instruction operation summary the tblrdl and the tblwtl instructions are used to read or write to bits<15:0> of program memory. tblrdl and tblwtl can access program memory in word or byte mode. the tblrdh and tblwth instructions are used to read or write to bits<23:16> of program memory. tblrdh and tblwth can access program memory in word or byte mode. a 24-bit program memory address is formed using bits<7:0> of the tblpag register and the effective address (ea) from a w register specified in the table instruction, as shown in figure 6-1. figure 6-1: addressing for table and nvm registers note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157). 0 program counter 24 bits nvmadru reg 8 bits 16 bits program using tblpag reg 8 bits working reg ea 16 bits using byte 24-bit ea 1/0 0 1/0 select table instruction nvmadr addressing counter using nvmadr reg ea user/configuration space select
dspic30f6011/6012/6013/6014 ds70117f-page 52 ? 2006 microchip technology inc. 6.4 rtsp operation the dspic30f flash program memory is organized into rows and panels. each row consists of 32 instruc- tions or 96 bytes. each panel consists of 128 rows or 4k x 24 instructions. rtsp allows the user to erase one row (32 instructions) at a time and to program four instructions at one time. rtsp may be used to program multiple program memory panels, but the table pointer must be changed at each panel boundary. each panel of program memory contains write latches that hold 32 instructions of programming data. prior to the actual programming operation, the write data must be loaded into the panel write latches. the data to be programmed into the panel is loaded in sequential order into the write latches: instruction 0, instruction 1, etc. the instruction words loaded must always be from a group of 32 boundary. the basic sequence for rtsp programming is to set up a table pointer, then do a series of tblwt instructions to load the write latches. programming is performed by setting the special bits in the nvmcon register. four tblwtl and four tblwth instructions are required to load the four instructions. if multiple panel program- ming is required, the table pointer needs to be changed and the next set of multiple write latches written. all of the table write operations are single word writes (2 instruction cycles) because only the table latches are written. a programming cycle is required for programming each row. the flash program memory is readable, writable, and erasable during normal operation over the entire v dd range. 6.5 control registers the four sfrs used to read and write the program flash memory are: ?nvmcon ? nvmadr ? nvmadru ? nvmkey 6.5.1 nvmcon register the nvmcon register controls which blocks are to be erased, which memory type is to be programmed and start of the programming cycle. 6.5.2 nvmadr register the nvmadr register is used to hold the lower two bytes of the effective address. the nvmadr register captures the ea<15:0> of the last table instruction that has been executed and selects the row to write. 6.5.3 nvmadru register the nvmadru register is used to hold the upper byte of the effective address. the nvmadru register cap- tures the ea<23:16> of the last table instruction that has been executed. 6.5.4 nvmkey register nvmkey is a write only register that is used for write protection. to start a programming or an erase sequence, the user must consecutively write 0x55 and 0xaa to the nvmkey register. refer to section 6.6 ?programming operations? for further details. note: the user can also directly write to the nvmadr and nvmadru registers to specify a program memory address for erasing or programming.
? 2006 microchip technology inc. ds70117f-page 53 dspic30f6011/6012/6013/6014 6.6 programming operations a complete programming sequence is necessary for programming or erasing the internal flash in rtsp mode. a programming operation is nominally 2 msec in duration and the processor stalls (waits) until the oper- ation is finished. setting the wr bit (nvmcon<15>) starts the operation, and the wr bit is automatically cleared when the operation is finished. 6.6.1 programming algorithm for program flash the user can erase and program one row of program flash memory at a time. the general process is: 1. read one row of program flash (32 instruction words) and store into data ram as a data ?image?. 2. update the data image with the desired new data. 3. erase program flash row. a) setup nvmcon register for multi-word, program flash, erase, and set wren bit. b) write address of row to be erased into nvmadru/nvmadr. c) write ? 55 ? to nvmkey. d) write ? aa ? to nvmkey. e) set the wr bit. this will begin erase cycle. f) cpu will stall for the duration of the erase cycle. g) the wr bit is cleared when erase cycle ends. 4. write 32 instruction words of data from data ram ?image? into the program flash write latches. 5. program 32 instruction words into program flash. a) setup nvmcon register for multi-word, program flash, program, and set wren bit. b) write ? 55 ? to nvmkey. c) write ? aa ? to nvmkey. d) set the wr bit. this will begin program cycle. e) cpu will stall for duration of the program cycle. f) the wr bit is cleared by the hardware when program cycle ends. 6. repeat steps 1 through 5 as needed to program desired amount of program flash memory. 6.6.2 erasing a row of program memory example 6-1 shows a code sequence that can be used to erase a row (32 instructions) of program memory. example 6-1: erasing a row of program memory ; setup nvmcon for erase operation, multi word write ; program memory selected, and writes enabled mov #0x4041,w0 ; mov w0 , nvmcon ; init nvmcon sfr ; init pointer to row to be erased mov #tblpage(prog_addr),w0 ; mov w0 , nvmadru ; initialize pm page boundary sfr mov #tbloffset(prog_addr),w0 ; intialize in-page ea[15:0] pointer mov w0, nvmadr ; initialize nvmadr sfr disi #5 ; block all interrupts with priority <7 for ; next 5 instructions mov #0x55,w0 mov w0 , nvmkey ; write the 0x55 key mov #0xaa,w1 ; mov w1 , nvmkey ; write the 0xaa key bset nvmcon,#wr ; start the erase sequence nop ; insert two nops after the erase nop ; command is asserted
dspic30f6011/6012/6013/6014 ds70117f-page 54 ? 2006 microchip technology inc. 6.6.3 loading write latches example 6-2 shows a sequence of instructions that can be used to load the 96 bytes of write latches. 32 tblwtl and 32 tblwth instructions are needed to load the write latches selected by the table pointer. example 6-2: loading write latches 6.6.4 initiating the programming sequence for protection, the write initiate sequence for nvmkey must be used to allow any erase or program operation to proceed. after the programming command has been executed, the user must wait for the programming time until programming is complete. the two instructions following the start of the programming sequence should be nop s. example 6-3: initiating a programming sequence ; set up a pointer to the first program memory location to be written ; program memory selected, and writes enabled mov #0x0000,w0 ; mov w0 , tblpag ; initialize pm page boundary sfr mov #0x6000,w0 ; an example program memory address ; perform the tblwt instructions to write the latches ; 0th_program_word mov #low_word_0,w2 ; mov #high_byte_0,w3 ; tblwtl w2 , [w0] ; write pm low word into program latch tblwth w3 , [w0++] ; write pm high byte into program latch ; 1st_program_word mov #low_word_1,w2 ; mov #high_byte_1,w3 ; tblwtl w2 , [w0] ; write pm low word into program latch tblwth w3 , [w0++] ; write pm high byte into program latch ; 2nd_program_word mov #low_word_2,w2 ; mov #high_byte_2,w3 ; tblwtl w2 , [w0] ; write pm low word into program latch tblwth w3 , [w0++] ; write pm high byte into program latch ? ? ? ; 31st_program_word mov #low_word_31,w2 ; mov #high_byte_31,w3 ; tblwtl w2 , [w0] ; write pm low word into program latch tblwth w3 , [w0++] ; write pm high byte into program latch note: in example 6-2, the contents of the upper byte of w3 has no effect. disi #5 ; block all interrupts with priority <7 for ; next 5 instructions mov #0x55,w0 ; mov w0 , nvmkey ; write the 0x55 key mov #0xaa,w1 ; mov w1 , nvmkey ; write the 0xaa key bset nvmcon,#wr ; start the erase sequence nop ; insert two nops after the erase nop ; command is asserted
? 2006 microchip technology inc. ds70117f-page 55 dspic30f6011/6012/6013/6014 table 6-1: nvm register map file name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 all resets nvmcon 0760 wr wren wrerr ? ? ? ?twri ? progop<6:0> 0000 0000 0000 0000 nvmadr 0762 nvmadr<15:0> uuuu uuuu uuuu uuuu nvmadru 0764 ? ? ? ? ? ? ? ? nvmadr<23:16> 0000 0000 uuuu uuuu nvmkey 0766 ? ? ? ? ? ? ? ? key<7:0> 0000 0000 0000 0000 legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 56 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 57 dspic30f6011/6012/6013/6014 7.0 data eeprom memory the data eeprom memory is readable and writable during normal operation over the entire v dd range. the data eeprom memory is directly mapped in the program memory address space. the four sfrs used to read and write the program flash memory are used to access data eeprom memory, as well. as described in section 6.5 ?control registers? , these registers are: ?nvmcon ? nvmadr ? nvmadru ? nvmkey the eeprom data memory allows read and write of single words and 16-word blocks. when interfacing to data memory, nvmadr in conjunction with the nvmadru register are used to address the eeprom location being accessed. tblrdl and tblwtl instructions are used to read and write data eeprom. the dspic30f devices have up to 8 kbytes (4k words) of data eeprom with an address range from 0x7ff000 to 0x7ffffe. a word write operation should be preceded by an erase of the corresponding memory location(s). the write typ- ically requires 2 ms to complete but the write time will vary with voltage and temperature. a program or erase operation on the data eeprom does not stop the instruction flow. the user is respon- sible for waiting for the appropriate duration of time before initiating another data eeprom write/erase operation. attempting to read the data eeprom while a programming or erase operation is in progress results in unspecified data. control bit wr initiates write operations similar to pro- gram flash writes. this bit cannot be cleared, only set, in software. they are cleared in hardware at the com- pletion of the write operation. the inability to clear the wr bit in software prevents the accidental or premature termination of a write operation. the wren bit, when set, will allow a write operation. on power-up, the wren bit is clear. the wrerr bit is set when a write operation is interrupted by a mclr reset or a wdt time-out reset during normal opera- tion. in these situations, following reset, the user can check the wrerr bit and rewrite the location. the address register nvmadr remains unchanged. 7.1 reading the data eeprom a tblrd instruction reads a word at the current pro- gram word address. this example uses w0 as a pointer to data eeprom. the result is placed in register w4 as shown in example 7-1. example 7-1: data eeprom read note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157). note: interrupt flag bit nvmif in the ifs0 regis- ter is set when write is complete. it must be cleared in software. mov #low_addr_word,w0 ; init pointer mov #high_addr_word,w1 mov w1 , tblpag tblrdl [ w0 ], w4 ; read data eeprom
dspic30f6011/6012/6013/6014 ds70117f-page 58 ? 2006 microchip technology inc. 7.2 erasing data eeprom 7.2.1 erasing a block of data eeprom in order to erase a block of data eeprom, the nvmadru and nvmadr registers must initially point to the block of memory to be erased. configure nvmcon for erasing a block of data eeprom, and set the erase and wren bits in the nvmcon register. setting the wr bit initiates the erase as shown in example 7-2. example 7-2: data eeprom block erase 7.2.2 erasing a word of data eeprom the nvmadru and nvmadr registers must point to the block. select erase a block of data flash, and set the erase and wren bits in the nvmcon register. setting the wr bit initiates the erase as shown in example 7-3. example 7-3: data eeprom word erase ; select data eeprom block, erase, wren bits mov #0x4045,w0 mov w0 , nvmcon ; initialize nvmcon sfr ; start erase cycle by setting wr after writing key sequence disi #5 ; block all interrupts with priority <7 for ; next 5 instructions mov #0x55,w0 ; mov w0 , nvmkey ; write the 0x55 key mov #0xaa,w1 ; mov w1 , nvmkey ; write the 0xaa key bset nvmcon,#wr ; initiate erase sequence nop nop ; erase cycle will complete in 2ms. cpu is not stalled for the data erase cycle ; user can poll wr bit, use nvmif or timer irq to determine erasure complete ; select data eeprom word, erase, wren bits mov #0x4044,w0 mov w0 , nvmcon ; start erase cycle by setting wr after writing key sequence disi #5 ; block all interrupts with priority <7 for ; next 5 instructions mov #0x55,w0 ; mov w0 , nvmkey ; write the 0x55 key mov #0xaa,w1 ; mov w1 , nvmkey ; write the 0xaa key bset nvmcon,#wr ; initiate erase sequence nop nop ; erase cycle will complete in 2ms. cpu is not stalled for the data erase cycle ; user can poll wr bit, use nvmif or timer irq to determine erasure complete
? 2006 microchip technology inc. ds70117f-page 59 dspic30f6011/6012/6013/6014 7.3 writing to the data eeprom to write an eeprom data location, the following sequence must be followed: 1. erase data eeprom word. a) select word, data eeprom erase, and set wren bit in nvmcon register. b) write address of word to be erased into nvmadr. c) enable nvm interrupt (optional). d) write ? 55 ? to nvmkey. e) write ? aa ? to nvmkey. f) set the wr bit. this will begin erase cycle. g) either poll nvmif bit or wait for nvmif interrupt. h) the wr bit is cleared when the erase cycle ends. 2. write data word into data eeprom write latches. 3. program 1 data word into data eeprom. a) select word, data eeprom program, and set wren bit in nvmcon register. b) enable nvm write done interrupt (optional). c) write ? 55 ? to nvmkey. d) write ? aa ? to nvmkey. e) set the wr bit. this will begin program cycle. f) either poll nvmif bit or wait for nvm interrupt. g) the wr bit is cleared when the write cycle ends. the write will not initiate if the above sequence is not exactly followed (write 0x55 to nvmkey, write 0xaa to nvmcon, then set wr bit) for each word. it is strongly recommended that interrupts be disabled during this code segment. additionally, the wren bit in nvmcon must be set to enable writes. this mechanism prevents accidental writes to data eeprom due to unexpected code exe- cution. the wren bit should be kept clear at all times except when updating the eeprom. the wren bit is not cleared by hardware. after a write sequence has been initiated, clearing the wren bit will not affect the current write cycle. the wr bit will be inhibited from being set unless the wren bit is set. the wren bit must be set on a previous instruc- tion. both wr and wren cannot be set with the same instruction. at the completion of the write cycle, the wr bit is cleared in hardware and the non-volatile memory write complete interrupt flag bit (nvmif) is set. the user may either enable this interrupt or poll this bit. nvmif must be cleared by software. 7.3.1 writing a word of data eeprom once the user has erased the word to be programmed, then a table write instruction is used to write one write latch, as shown in example 7-4. example 7-4: data eeprom word write ; point to data memory mov #low_addr_word,w0 ; init pointer mov #high_addr_word,w1 mov w1 , tblpag mov #low(word),w2 ; get data tblwtl w2 , [ w0] ; write data ; the nvmadr captures last table access address ; select data eeprom for 1 word op mov #0x4004,w0 mov w0 , nvmcon ; operate key to allow write operation disi #5 ; block all interrupts with priority <7 for ; next 5 instructions mov #0x55,w0 mov w0 , nvmkey ; write the 0x55 key mov #0xaa,w1 mov w1 , nvmkey ; write the 0xaa key bset nvmcon,#wr ; initiate program sequence nop nop ; write cycle will complete in 2ms. cpu is not stalled for the data write cycle ; user can poll wr bit, use nvmif or timer irq to determine write complete
dspic30f6011/6012/6013/6014 ds70117f-page 60 ? 2006 microchip technology inc. 7.3.2 writing a block of data eeprom to write a block of data eeprom, write to all sixteen latches first, then set the nvmcon register and program the block. example 7-5: data eeprom block write mov #low_addr_word,w0 ; init pointer mov #high_addr_word,w1 mov w1 , tblpag mov #data1,w2 ; get 1st data tblwtl w2 , [ w0]++ ; write data mov #data2,w2 ; get 2nd data tblwtl w2 , [ w0]++ ; write data mov #data3,w2 ; get 3rd data tblwtl w2 , [ w0]++ ; write data mov #data4,w2 ; get 4th data tblwtl w2 , [ w0]++ ; write data mov #data5,w2 ; get 5th data tblwtl w2 , [ w0]++ ; write data mov #data6,w2 ; get 6th data tblwtl w2 , [ w0]++ ; write data mov #data7,w2 ; get 7th data tblwtl w2 , [ w0]++ ; write data mov #data8,w2 ; get 8th data tblwtl w2 , [ w0]++ ; write data mov #data9,w2 ; get 9th data tblwtl w2 , [ w0]++ ; write data mov #data10,w2 ; get 10th data tblwtl w2 , [ w0]++ ; write data mov #data11,w2 ; get 11th data tblwtl w2 , [ w0]++ ; write data mov #data12,w2 ; get 12th data tblwtl w2 , [ w0]++ ; write data mov #data13,w2 ; get 13th data tblwtl w2 , [ w0]++ ; write data mov #data14,w2 ; get 14th data tblwtl w2 , [ w0]++ ; write data mov #data15,w2 ; get 15th data tblwtl w2 , [ w0]++ ; write data mov #data16,w2 ; get 16th data tblwtl w2 , [ w0]++ ; write data. the nvmadr captures last table access address. mov #0x400a,w0 ; select data eeprom for multi word op mov w0 , nvmcon ; operate key to allow program operation disi #5 ; block all interrupts with priority <7 for ; next 5 instructions mov #0x55,w0 mov w0 , nvmkey ; write the 0x55 key mov #0xaa,w1 mov w1 , nvmkey ; write the 0xaa key bset nvmcon,#wr ; start write cycle nop nop
? 2006 microchip technology inc. ds70117f-page 61 dspic30f6011/6012/6013/6014 7.4 write verify depending on the application, good programming practice may dictate that the value written to the mem- ory should be verified against the original value. this should be used in applications where excessive writes can stress bits near the specification limit. 7.5 protection against spurious write there are conditions when the device may not want to write to the data eeprom memory. to protect against spurious eeprom writes, various mechanisms have been built-in. on power-up, the wren bit is cleared; also, the power-up timer prevents eeprom write. the write initiate sequence and the wren bit together help prevent an accidental write during brown-out, power glitch, or software malfunction.
dspic30f6011/6012/6013/6014 ds70117f-page 62 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 63 dspic30f6011/6012/6013/6014 8.0 i/o ports all of the device pins (except v dd , v ss , mclr and osc1/clki) are shared between the peripherals and the parallel i/o ports. all i/o input ports feature schmitt trigger inputs for improved noise immunity. 8.1 parallel i/o (pio) ports when a peripheral is enabled and the peripheral is actively driving an associated pin, the use of the pin as a general purpose output pin is disabled. the i/o pin may be read but the output driver for the parallel port bit will be disabled. if a peripheral is enabled but the peripheral is not actively driving a pin, that pin may be driven by a port. all port pins have three registers directly associated with the operation of the port pin. the data direction register (trisx) determines whether the pin is an input or an output. if the data direction bit is a ? 1 ?, then the pin is an input. all port pins are defined as inputs after a reset. reads from the latch (latx), read the latch. writes to the latch, write the latch (latx). reads from the port (portx), read the port pins and writes to the port pins, write the latch (latx). any bit and its associated data and control registers that are not valid for a particular device will be dis- abled. that means the corresponding latx and trisx registers and the port pin will read as zeros. when a pin is shared with another peripheral or func- tion that is defined as an input only, it is nevertheless regarded as a dedicated port because there is no other competing source of outputs. an example is the int4 pin. the format of the registers for porta are shown in table 8-1. the trisa (data direction control) register controls the direction of the ra<7:0> pins, as well as the intx pins and the v ref pins. the lata register supplies data to the outputs and is readable/writable. reading the porta register yields the state of the input pins, while writing the porta register modifies the contents of the lata register. a parallel i/o (pio) port that shares a pin with a periph- eral is, in general, subservient to the peripheral. the peripheral?s output buffer data and control signals are provided to a pair of multiplexers. the multiplexers select whether the peripheral or the associated port has ownership of the output data and control signals of the i/o pad cell. figure 8-2 shows how ports are shared with other peripherals and the associated i/o cell (pad) to which they are connected. table 8-2 through table 8-9 show the formats of the registers for the shared ports, portb through portg. figure 8-1: block diagram of a dedicated port structure note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). note: the actual bits in use vary between devices. q d ck wr lat + tris latch i/o pad wr port data bus q d ck data latch read lat read port read tris wr tris i/o cell dedicated port module
dspic30f6011/6012/6013/6014 ds70117f-page 64 ? 2006 microchip technology inc. 8.2 configuring analog port pins the use of the adpcfg and tris registers control the operation of the a/d port pins. the port pins that are desired as analog inputs must have their correspond- ing tris bit set (input). if the tris bit is cleared (out- put), the digital output level (v oh or v ol ) will be converted. when reading the port register, all pins configured as analog input channels will read as cleared (a low level). pins configured as digital inputs will not convert an ana- log input. analog levels on any pin that is defined as a digital input (including the anx pins) may cause the input buffer to consume current that exceeds the device specifications. figure 8-2: block diagram of a shared port structure q d ck wr lat + tris latch i/o pad wr port data bus q d ck data latch read lat read port read tris 1 0 1 0 wr tris peripheral output data output enable peripheral input data i/o cell peripheral module peripheral output enable pio module output multiplexers output data input data peripheral module enable
? 2006 microchip technology inc. ds70117f-page 65 dspic30f6011/6012/6013/6014 table 8-1: porta register map for dspic30f6013/6014 table 8-2: portb register map for dspic30f6011/6012/6013/6014 table 8-3: portc register map for dspic30f6011/6012 table 8-4: portc register map for dspic30f6013/6014 sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisa 02c0 trisa15 trisa14 trisa13 trisa12 ? trisa10 trisa9 ? trisa7 trisa6 ? ? ? ? ? ? 1111 0110 1100 0000 porta 02c2 ra15 ra14 ra13 ra12 ? ra10 ra9 ?ra7 ra6 ? ? ? ? ? ? 0000 0000 0000 0000 lata 02c4 lata15 lata14 lata13 lata12 ? lata10 lata9 ?lata7lata6 ? ? ? ? ? ? 0000 0000 0000 0000 note 1: porta is not implemented in the dspic30f6011/6012 devices. 2: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisb 02c6 trisb15 trisb14 trisb13 trisb12 trisb11 trisb10 trisb9 trisb8 trisb7 trisb6 trisb5 trisb4 trisb3 trisb2 trisb1 trisb0 1111 1111 1111 1111 portb 02c8 rb15 rb14 rb13 rb12 rb11 rb10 rb9 rb8 rb7 rb6 rb5 rb4 rb3 rb2 rb1 rb0 0000 0000 0000 0000 latb 02cb latb15 latb14 latb13 latb12 latb11 latb10 latb9 latb8 latb7 latb6 latb5 latb4 latb3 latb2 latb1 latb0 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisc 02cc trisc15 trisc14 trisc13 ? ? ? ? ? ? ? ? ? ? trisc2 trisc1 ? 1110 0000 0000 0110 portc 02ce rc15 rc14 rc13 ? ? ? ? ? ? ? ? ? ? rc2 rc1 ? 0000 0000 0000 0000 latc 02d0 latc15 latc14 latc13 ? ? ? ? ? ? ? ? ? ?latc2latc1 ? 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisc 02cc trisc15 trisc14 trisc13 ? ? ? ? ? ? ? ? trisc4 trisc3 trisc2 trisc1 ? 1110 0000 0001 1110 portc 02ce rc15 rc14 rc13 ? ? ? ? ? ? ? ? rc4 rc3 rc2 rc1 ? 0000 0000 0000 0000 latc 02d0 latc15 latc14 latc13 ? ? ? ? ? ? ? ? latc4 latc3 latc2 latc1 ? 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 66 ? 2006 microchip technology inc. table 8-5: portd register map for dspic30f6011/6012 table 8-6: portd register map for dspic30f6013/6014 table 8-7: portf register map for dspic30f6011/6012 table 8-8: portf register map for dspic30f6013/6014 table 8-9: portg register map for dspic30f6011/6012/6013/6014 sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisd 02d2 ? ? ? ? trisd11 trisd10 trisd9 trisd8 trisd7 trisd6 tri sd5 trisd4 trisd3 trisd2 trisd1 trisd0 0000 1111 1111 1111 portd 02d4 ? ? ? ? rd11 rd10 rd9 rd8 rd7 rd6 rd5 rd4 rd3 rd2 rd1 rd0 0000 0000 0000 0000 latd 02d6 ? ? ? ? latd11 latd10 latd9 latd8 latd7 latd6 latd5 latd4 latd3 latd2 latd1 latd0 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisd 02d2 trisd15 trisd14 trisd13 trisd12 trisd11 trisd10 trisd9 trisd8 trisd7 trisd6 tri sd5 trisd4 trisd3 trisd2 trisd1 trisd0 1111 1111 1111 1111 portd 02d4 rd15 rd14 rd13 rd12 rd11 rd10 rd9 rd8 rd7 rd6 rd5 rd4 rd3 rd2 rd1 rd0 0000 0000 0000 0000 latd 02d6 latd15 latd14 latd13 latd12 latd11 latd10 latd9 latd8 latd7 latd6 latd5 latd4 latd3 latd2 latd1 latd0 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisf 02de ? ? ? ? ? ? ? ? ? trisf6 trisf5 trisf4 tri sf3 trisf2 trisf1 trisf0 0000 0000 0111 1111 portf 02e0 ? ? ? ? ? ? ? ? ? rf6 rf5 rf4 rf3 rf2 rf1 rf0 0000 0000 0000 0000 latf 02e2 ? ? ? ? ? ? ? ? ? latf6 latf5 latf4 latf3 latf2 latf1 latf0 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisf 02de ? ? ? ? ? ? ? trisf8 trisf7 trisf6 trisf5 tri sf4 trisf3 trisf2 trisf1 trisf0 0000 0001 1111 1111 portf 02e0 ? ? ? ? ? ? ? rf8 rf7 rf6 rf5 rf4 rf3 rf2 rf1 rf0 0000 0000 0000 0000 latf 02e2 ? ? ? ? ? ? ? latf8 latf7 latf6 latf5 latf4 latf3 latf2 latf1 latf0 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state trisg 02e4 trisg15 trisg14 trisg13 trisg12 ? ? trisg9 trisg8 trisg7 trisg6 ? ? trisg3 trisg2 t risg1 trisg0 1111 0011 1100 1111 portg 02e6 rg15 rg14 rg13 rg12 ? ? rg9 rg8 rg7 rg6 ? ? rg3 rg2 rg1 rg0 0000 0000 0000 0000 latg 02e8 latg15 latg14 latg13 latg12 ? ? latg9 latg8 latg7 latg6 ? ? latg3 latg2 latg1 latg0 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 67 dspic30f6011/6012/6013/6014 8.3 input change notification module the input change notification module provides the dspic30f devices the ability to generate interrupt requests to the processor, in response to a change of state on selected input pins. this module is capable of detecting input change of states even in sleep mode, when the clocks are disabled. there are up to 24 exter- nal signals (cn0 through cn23) that may be selected (enabled) for generating an interrupt request on a change of state. table 8-10: input change notification register map for dspic30f6011/6012 (bits 15-8) table 8-11: input change notification regist er map for dspic30f6011/6012 (bits 7-0) table 8-12: input change notification register map for dspic30f6013/6014 (bits 15-8) table 8-13: input change notification regist er map for dspic30f6013/6014 (bits 7-0) sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 reset state cnen1 00c0 cn15ie cn14ie cn13ie cn12ie cn11ie cn10ie cn9ie cn8ie 0000 0000 0000 0000 cnen2 00c2 ? ? ? ? ? ? ? ? 0000 0000 0000 0000 cnpu1 00c4 cn15pue cn14pue cn13pue cn12pue cn11pue cn10pue cn9pue cn8pue 0000 0000 0000 0000 cnpu2 00c6 ? ? ? ? ? ? ? ? 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state cnen1 00c0 cn7ie cn6ie cn5ie cn4ie cn3ie cn2ie cn1ie cn0ie 0000 0000 0000 0000 cnen2 00c2 ? ? ? ? ? cn18ie cn17ie cn16ie 0000 0000 0000 0000 cnpu1 00c4 cn7pue cn6pue cn5pue cn4pue cn3pue cn2pue cn1pue cn0pue 0000 0000 0000 0000 cnpu2 00c6 ? ? ? ? ? cn18pue cn17pue cn16pue 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 reset state cnen1 00c0 cn15ie cn14ie cn13ie cn12ie cn11ie cn10ie cn9ie cn8ie 0000 0000 0000 0000 cnen2 00c2 ? ? ? ? ? ? ? ? 0000 0000 0000 0000 cnpu1 00c4 cn15pue cn14pue cn13pue cn12pue cn11pue cn10pue cn9pue cn8pue 0000 0000 0000 0000 cnpu2 00c6 ? ? ? ? ? ? ? ? 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state cnen1 00c0 cn7ie cn6ie cn5ie cn4ie cn3ie cn2ie cn1ie cn0ie 0000 0000 0000 0000 cnen2 00c2 cn23ie cn22ie cn21ie cn20ie cn19ie cn18ie cn17ie cn16ie 0000 0000 0000 0000 cnpu1 00c4 cn7pue cn6pue cn5pue cn4pue cn3pue cn2pue cn1pue cn0pue 0000 0000 0000 0000 cnpu2 00c6 cn23pue cn22pue cn21pue cn20pue cn19pue cn18pue cn17pue cn16pue 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 68 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 69 dspic30f6011/6012/6013/6014 9.0 timer1 module this section describes the 16-bit general purpose timer1 module and associated operational modes. figure 9-1 depicts the simplified block diagram of the 16-bit timer1 module. the following sections provide a detailed description including setup and control registers, along with asso- ciated block diagrams for the operational modes of the timers. the timer1 module is a 16-bit timer which can serve as the time counter for the real-time clock, or operate as a free-running interval timer/counter. the 16-bit timer has the following modes: ? 16-bit timer ? 16-bit synchronous counter ? 16-bit asynchronous counter further, the following operational characteristics are supported: ? timer gate operation ? selectable prescaler settings ? timer operation during cpu idle and sleep modes ? interrupt on 16-bit period register match or falling edge of external gate signal these operating modes are determined by setting the appropriate bit(s) in the 16-bit sfr, t1con. figure 9-1 presents a block diagram of the 16-bit timer module. 16-bit timer mode: in the 16-bit timer mode, the timer increments on every instruction cycle up to a match value preloaded into the period register pr1, then resets to ? 0 ? and continues to count. when the cpu goes into the idle mode, the timer will stop incrementing unless the tsidl (t1con<13>) bit = 0 . if tsidl = 1 , the timer module logic will resume the incrementing sequence upon termination of the cpu idle mode. 16-bit synchronous counter mode: in the 16-bit synchronous counter mode, the timer increments on the rising edge of the applied external clock signal which is synchronized with the internal phase clocks. the timer counts up to a match value preloaded in pr1, then resets to ? 0 ? and continues. when the cpu goes into the idle mode, the timer will stop incrementing unless the respective tsidl bit = 0 . if tsidl = 1 , the timer module logic will resume the incrementing sequence upon termination of the cpu idle mode. 16-bit asynchronous counter mode: in the 16-bit asynchronous counter mode, the timer increments on every rising edge of the applied external clock signal. the timer counts up to a match value preloaded in pr1, then resets to ? 0 ? and continues. when the timer is configured for the asynchronous mode of operation and the cpu goes into the idle mode, the timer will stop incrementing if tsidl = 1 . note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046).
dspic30f6011/6012/6013/6014 ds70117f-page 70 ? 2006 microchip technology inc. figure 9-1: 16-bit timer1 module block diagram 9.1 timer gate operation the 16-bit timer can be placed in the gated time accu- mulation mode. this mode allows the internal t cy to increment the respective timer when the gate input sig- nal (t1ck pin) is asserted high. control bit tgate (t1con<6>) must be set to enable this mode. the timer must be enabled (ton = 1 ) and the timer clock source set to internal (tcs = 0 ). when the cpu goes into the idle mode, the timer will stop incrementing unless tsidl = 0 . if tsidl = 1 , the timer will resume the incrementing sequence upon termination of the cpu idle mode. 9.2 timer prescaler the input clock (f osc /4 or external clock) to the 16-bit timer has a prescale option of 1:1, 1:8, 1:64 and 1:256, selected by control bits tckps<1:0> (t1con<5:4>). the prescaler counter is cleared when any of the following occurs: ? a write to the tmr1 register ? a write to the t1con register ? device reset, such as por and bor however, if the timer is disabled (ton = 0 ), then the timer prescaler cannot be reset since the prescaler clock is halted. tmr1 is not cleared when t1con is written. it is cleared by writing to the tmr1 register. 9.3 timer operation during sleep mode during cpu sleep mode, the timer will operate if: ? the timer module is enabled (ton = 1 ) and ? the timer clock source is selected as external (tcs = 1 ) and ? the tsync bit (t1con<2>) is asserted to a logic ? 0 ? which defines the external clock source as asynchronous. when all three conditions are true, the timer will con- tinue to count up to the period register and be reset to 0x0000. when a match between the timer and the period regis- ter occurs, an interrupt can be generated if the respective timer interrupt enable bit is asserted. ton sync sosci sosco/ pr1 t1if equal comparator x 16 tmr1 reset lposcen event flag 1 0 tsync q qd ck tgate tckps<1:0> prescaler 1, 8, 64, 256 2 tgate t cy 1 0 t1ck tcs 1 x 0 1 tgate 0 0 gate sync
? 2006 microchip technology inc. ds70117f-page 71 dspic30f6011/6012/6013/6014 9.4 timer interrupt the 16-bit timer has the ability to generate an interrupt on period match. when the timer count matches the period register, the t1if bit is asserted and an interrupt will be generated if enabled. the t1if bit must be cleared in software. the timer interrupt flag, t1if, is located in the ifs0 control register in the interrupt controller. when the gated time accumulation mode is enabled, an interrupt will also be generated on the falling edge of the gate signal (at the end of the accumulation cycle). enabling an interrupt is accomplished via the respec- tive timer interrupt enable bit, t1ie. the timer interrupt enable bit is located in the iec0 control register in the interrupt controller. 9.5 real-time clock timer1, when operating in real-time clock (rtc) mode, provides time of day and event time-stamping capabilities. key operational features of the rtc are: ? operation from 32 khz lp oscillator ? 8-bit prescaler ? low power ? real-time clock interrupts these operating modes are determined by setting the appropriate bit(s) in the t1con control register. figure 9-2: recommended components for timer1 lp oscillator rtc 9.5.1 rtc oscillator operation when the ton = 1 , tcs = 1 and tgate = 0 , the timer increments on the rising edge of the 32 khz lp oscilla- tor output signal, up to the value specified in the period register and is then reset to ? 0 ?. the tsync bit must be asserted to a logic ? 0 ? (asynchronous mode) for correct operation. enabling lposcen (osccon<1>) will disable the normal timer and counter modes and enable a timer carry-out wake-up event. when the cpu enters sleep mode, the rtc will con- tinue to operate provided the 32 khz external crystal oscillator is active and the control bits have not been changed. the tsidl bit should be cleared to ? 0 ? in order for rtc to continue operation in idle mode. 9.5.2 rtc interrupts when an interrupt event occurs, the respective interrupt flag, t1if, is asserted and an interrupt will be generated if enabled. the t1if bit must be cleared in software. the respective timer interrupt flag, t1if, is located in the ifs0 status register in the interrupt controller. enabling an interrupt is accomplished via the respec- tive timer interrupt enable bit, t1ie. the timer interrupt enable bit is located in the iec0 control register in the interrupt controller. sosci sosco r c1 c2 dspic30fxxxx 32.768 khz xtal c1 = c2 = 18 pf; r = 100k
dspic30f6011/6012/6013/6014 ds70117f-page 72 ? 2006 microchip technology inc. table 9-1: timer1 register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state tmr1 0100 timer1 register uuuu uuuu uuuu uuuu pr1 0102 period register 1 1111 1111 1111 1111 t1con 0104 ton ?tsidl ? ? ? ? ? ? tgate tckps1 tckps0 ?tsynctcs ? 0000 0000 0000 0000 legend: u = uninitialized bit note: refer to ?dspic30f family reference manual ? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 73 dspic30f6011/6012/6013/6014 10.0 timer2/3 module this section describes the 32-bit general purpose timer module (timer2/3) and associated operational modes. figure 10-1 depicts the simplified block dia- gram of the 32-bit timer2/3 module. figure 10-2 and figure 10-3 show timer2/3 configured as two independent 16-bit timers, timer2 and timer3, respectively. the timer2/3 module is a 32-bit timer (which can be configured as two 16-bit timers) with selectable operating modes. these timers are utilized by other peripheral modules, such as: ? input capture ? output compare/simple pwm the following sections provide a detailed description, including setup and control registers, along with asso- ciated block diagrams for the operational modes of the timers. the 32-bit timer has the following modes: ? two independent 16-bit timers (timer2 and timer3) with all 16-bit operating modes (except asynchronous counter mode) ? single 32-bit timer operation ? single 32-bit synchronous counter further, the following operational characteristics are supported: ? adc event trigger ? timer gate operation ? selectable prescaler settings ? timer operation during idle and sleep modes ? interrupt on a 32-bit period register match these operating modes are determined by setting the appropriate bit(s) in the 16-bit t2con and t3con sfrs. for 32-bit timer/counter operation, timer2 is the least significant word and timer3 is the most significant word of the 32-bit timer. 16-bit timer mode: in the 16-bit mode, timer2 and timer3 can be configured as two independent 16-bit timers. each timer can be set up in either 16-bit timer mode or 16-bit synchronous counter mode. see section 9.0 ?timer1 module? , timer1 module for details on these two operating modes. the only functional difference between timer2 and timer3 is that timer2 provides synchronization of the clock prescaler output. this is useful for high frequency external clock inputs. 32-bit timer mode: in the 32-bit timer mode, the timer increments on every instruction cycle, up to a match value preloaded into the combined 32-bit period register pr3/pr2, then resets to ? 0 ? and continues to count. for synchronous 32-bit reads of the timer2/timer3 pair, reading the least significant word (tmr2 register) will cause the most significant word (msw) to be read and latched into a 16-bit holding register, termed tmr3hld. for synchronous 32-bit writes, the holding register (tmr3hld) must first be written to. when followed by a write to the tmr2 register, the contents of tmr3hld will be transferred and latched into the msb of the 32-bit timer (tmr3). 32-bit synchronous counter mode: in the 32-bit synchronous counter mode, the timer increments on the rising edge of the applied external clock signal which is synchronized with the internal phase clocks. the timer counts up to a match value preloaded in the combined 32-bit period register pr3/pr2, then resets to ? 0 ? and continues. when the timer is configured for the synchronous counter mode of operation and the cpu goes into the idle mode, the timer will stop incrementing unless the tsidl (t2con<13>) bit = 0 . if tsidl = 1 , the timer module logic will resume the incrementing sequence upon termination of the cpu idle mode. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). note: for 32-bit timer operation, t3con control bits are ignored. only t2con control bits are used for setup and control. timer2 clock and gate inputs are utilized for the 32-bit timer module but an interrupt is gen- erated with the timer3 interrupt flag (t3if) and the interrupt is enabled with the timer3 interrupt enable bit (t3ie).
dspic30f6011/6012/6013/6014 ds70117f-page 74 ? 2006 microchip technology inc. figure 10-1: 32-bit timer2/3 block diagram tmr3 tmr2 t3if equal comparator x 32 pr3 pr2 reset lsb msb event flag note: timer configuration bit t32 (t2con<3>) must be set to ? 1 ? for a 32-bit timer/counter operation. all control bits are respective to the t2con register. data bus<15:0> read tmr2 write tmr2 16 16 16 q qd ck tgate (t2con<6>) (t2con<6>) tgate 0 1 ton tckps<1:0> 2 t cy tcs 1 x 0 1 tgate 0 0 gate t2ck sync adc event trigger sync tmr3hld prescaler 1, 8, 64, 256
? 2006 microchip technology inc. ds70117f-page 75 dspic30f6011/6012/6013/6014 figure 10-2: 16-bit ti mer2 block diagram figure 10-3: 16-bit ti mer3 block diagram ton sync pr2 t2if equal comparator x 16 tmr2 reset event flag tgate tckps<1:0> 2 tgate t cy 1 0 tcs 1 x 0 1 tgate 0 0 gate t2ck sync prescaler 1, 8, 64, 256 q q d ck ton pr3 t3if equal comparator x 16 tmr3 reset event flag tgate tckps<1:0> 2 tgate t cy 1 0 tcs 1 x 0 1 tgate 0 0 t3ck adc event trigger sync q qd ck prescaler 1, 8, 64, 256
dspic30f6011/6012/6013/6014 ds70117f-page 76 ? 2006 microchip technology inc. 10.1 timer gate operation the 32-bit timer can be placed in the gated time accu- mulation mode. this mode allows the internal t cy to increment the respective timer when the gate input sig- nal (t2ck pin) is asserted high. control bit tgate (t2con<6>) must be set to enable this mode. when in this mode, timer2 is the originating clock source. the tgate setting is ignored for timer3. the timer must be enabled (ton = 1 ) and the timer clock source set to internal (tcs = 0 ). the falling edge of the external signal terminates the count operation but does not reset the timer. the user must reset the timer in order to start counting from zero. 10.2 adc event trigger when a match occurs between the 32-bit timer (tmr3/ tmr2) and the 32-bit combined period register (pr3/ pr2), or between the 16-bit timer tmr3 and the 16-bit period register pr3, a special adc trigger event signal is generated by timer3. 10.3 timer prescaler the input clock (f osc /4 or external clock) to the timer has a prescale option of 1:1, 1:8, 1:64, and 1:256, selected by control bits tckps<1:0> (t2con<5:4> and t3con<5:4>). for the 32-bit timer operation, the originating clock source is timer2. the prescaler oper- ation for timer3 is not applicable in this mode. the prescaler counter is cleared when any of the following occurs: ? a write to the tmr2/tmr3 register ? a write to the t2con/t3con register ? device reset, such as por and bor however, if the timer is disabled (ton = 0 ), then the timer 2 prescaler cannot be reset since the prescaler clock is halted. tmr2/tmr3 is not cleared when t2con/t3con is written. 10.4 timer operation during sleep mode during cpu sleep mode, the timer will not operate because the internal clocks are disabled. 10.5 timer interrupt the 32-bit timer module can generate an interrupt on period match or on the falling edge of the external gate signal. when the 32-bit timer count matches the respective 32-bit period register, or the falling edge of the external ?gate? signal is detected, the t3if bit (ifs0<7>) is asserted and an interrupt will be gener- ated if enabled. in this mode, the t3if interrupt flag is used as the source of the interrupt. the t3if bit must be cleared in software. enabling an interrupt is accomplished via the respective timer interrupt enable bit, t3ie (iec0<7>).
? 2006 microchip technology inc. ds70117f-page 77 dspic30f6011/6012/6013/6014 table 10-1: timer2/3 register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state tmr2 0106 timer2 register uuuu uuuu uuuu uuuu tmr3hld 0108 timer3 holding register (for 32-bit timer operations only) uuuu uuuu uuuu uuuu tmr3 010a timer3 register uuuu uuuu uuuu uuuu pr2 010c period register 2 1111 1111 1111 1111 pr3 010e period register 3 1111 1111 1111 1111 t2con 0110 ton ?tsidl ? ? ? ? ? ? tgate tckps1 tckps0 t32 ?tcs ? 0000 0000 0000 0000 t3con 0112 ton ?tsidl ? ? ? ? ? ? tgate tckps1 tckps0 ? ?tcs ? 0000 0000 0000 0000 legend: u = uninitialized bit note: refer to dspic30f family reference manua l (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 78 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 79 dspic30f6011/6012/6013/6014 11.0 timer4/5 module this section describes the second 32-bit general pur- pose timer module (timer4/5) and associated opera- tional modes. figure 11-1 depicts the simplified block diagram of the 32-bit timer4/5 module. figure 11-2 and figure 11-3 show timer4/5 configured as two indepen- dent 16-bit timers, timer4 and timer5, respectively. the timer4/5 module is similar in operation to the timer2/3 module. however, there are some differences which are as follows: ? the timer4/5 module does not support the adc event trigger feature ? timer4/5 can not be utilized by other peripheral modules, such as input capture and output compare the operating modes of the timer4/5 module are deter- mined by setting the appropriate bit(s) in the 16-bit t4con and t5con sfrs. for 32-bit timer/counter operation, timer4 is the lsw and timer5 is the msw of the 32-bit timer. figure 11-1: 32-bit timer4/5 block diagram note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). note: for 32-bit timer operation, t5con control bits are ignored. only t4con control bits are used for setup and control. timer4 clock and gate inputs are utilized for the 32-bit timer module but an interrupt is gen- erated with the timer5 interrupt flag (t5if) and the interrupt is enabled with the timer5 interrupt enable bit (t5ie). tmr5 tmr4 t5if equal comparator x 32 pr5 pr4 reset lsb msb event flag note: timer configuration bit t45 (t4con<3>) must be set to ? 1 ? for a 32-bit timer/counter operation. all control bits are respective to the t4con register. data bus<15:0> tmr5hld read tmr4 write tmr4 16 16 16 q qd ck tgate (t4con<6>) (t4con<6>) tgate 0 1 ton tckps<1:0> prescaler 1, 8, 64, 256 2 t cy tcs 1 x 0 1 tgate 0 0 gate t4ck sync sync
dspic30f6011/6012/6013/6014 ds70117f-page 80 ? 2006 microchip technology inc. figure 11-2: 16-bit timer4 block diagram figure 11-3: 16-bit timer5 block diagram ton sync pr4 t4if equal comparator x 16 tmr4 reset event flag tgate tckps<1:0> prescaler 1, 8, 64, 256 2 tgate t cy 1 0 tcs 1 x 0 1 tgate 0 0 gate t4ck sync q q d ck ton pr5 t5if equal comparator x 16 tmr5 reset event flag tgate tckps<1:0> prescaler 1, 8, 64, 256 2 tgate t cy 1 0 tcs 1 x 0 1 tgate 0 0 t5ck adc event trigger sync q qd ck note: in the dspic30f6011 and dspic30f6012 devices, there is no t5ck pin. therefore, in this device the following modes should not be used for timer5: 1: tcs = 1 (16-bit counter) 2: tcs = 0 , tgate = 1 (gated time accumulation)
? 2006 microchip technology inc. ds70117f-page 81 dspic30f6011/6012/6013/6014 table 11-1: timer4/5 register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state tmr4 0114 timer 4 register uuuu uuuu uuuu uuuu tmr5hld 0116 timer 5 holding register (for 32-bit operations only) uuuu uuuu uuuu uuuu tmr5 0118 timer 5 register uuuu uuuu uuuu uuuu pr4 011a period register 4 1111 1111 1111 1111 pr5 011c period register 5 1111 1111 1111 1111 t4con 011e ton ?tsidl ? ? ? ? ? ? tgate tckps1 tckps0 t45 ?tcs ? 0000 0000 0000 0000 t5con 0120 ton ?tsidl ? ? ? ? ? ? tgate tckps1 tckps0 ? ?tcs ? 0000 0000 0000 0000 legend: u = uninitialized note: refer to ?dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 82 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 83 dspic30f6011/6012/6013/6014 12.0 input capture module this section describes the input capture module and associated operational modes. the features provided by this module are useful in applications requiring fre- quency (period) and pulse measurement. figure 12-1 depicts a block diagram of the input capture module. input capture is useful for such modes as: ? frequency/period/pulse measurements ? additional sources of external interrupts the key operational features of the input capture module are: ? simple capture event mode ? timer2 and timer3 mode selection ? interrupt on input capture event these operating modes are determined by setting the appropriate bits in the icxcon register (where x = 1,2,...,n). the dspic dsc devices contain up to 8 capture channels (i.e., the maximum value of n is 8). 12.1 simple capture event mode the simple capture events in the dspic30f product family are: ? capture every falling edge ? capture every rising edge ? capture every 4th rising edge ? capture every 16th rising edge ? capture every rising and falling edge these simple input capture modes are configured by setting the appropriate bits icm<2:0> (icxcon<2:0>). 12.1.1 capture prescaler there are four input capture prescaler settings speci- fied by bits icm<2:0> (icxcon<2:0>). whenever the capture channel is turned off, the prescaler counter will be cleared. in addition, any reset will clear the prescaler counter. figure 12-1: input capture mode block diagram note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). icxbuf prescaler icx pin icm<2:0> mode select 3 note: where ?x? is shown, reference is m ade to the registers or bits associat ed to the respective input capture channels 1 through n. 10 set flag icxif ictmr t2_cnt t3_cnt edge detection logic clock synchronizer 1, 4, 16 from gp timer module 16 16 fifo r/w logic ici<1:0> icbne, icov icxcon interrupt logic set flag icxif data bus
dspic30f6011/6012/6013/6014 ds70117f-page 84 ? 2006 microchip technology inc. 12.1.2 capture buffer operation each capture channel has an associated fifo buffer which is four 16-bit words deep. there are two status flags which provide status on the fifo buffer: ? icbfne ? input capture buffer not empty ? icov ? input capture overflow the icbfne will be set on the first input capture event and remain set until all capture events have been read from the fifo. as each word is read from the fifo, the remaining words are advanced by one position within the buffer. in the event that the fifo is full with four capture events and a fifth capture event occurs prior to a read of the fifo, an overflow condition will occur and the icov bit will be set to a logic ? 1 ?. the fifth capture event is lost and is not stored in the fifo. no additional events will be captured until all four events have been read from the buffer. if a fifo read is performed after the last read and no new capture event has been received, the read will yield indeterminate results. 12.1.3 timer2 and timer3 selection mode the input capture module consists of up to 8 input cap- ture channels. each channel can select between one of two timers for the time base, timer2 or timer3. selection of the timer resource is accomplished through sfr bit, ictmr (icxcon<7>). timer3 is the default timer resource available for the input capture module. 12.1.4 hall sensor mode when the input capture module is set for capture on every edge, rising and falling, icm<2:0> = 001 , the fol- lowing operations are performed by the input capture logic: ? the input capture interrupt flag is set on every edge, rising and falling. ? the interrupt on capture mode setting bits, ici<1:0>, is ignored since every capture generates an interrupt. ? a capture overflow condition is not generated in this mode. 12.2 input capture operation during sleep and idle modes an input capture event will generate a device wake-up or interrupt, if enabled, if the device is in cpu idle or sleep mode. independent of the timer being enabled, the input cap- ture module will wake-up from the cpu sleep or idle mode when a capture event occurs if icm<2:0> = 111 and the interrupt enable bit is asserted. the same wake- up can generate an interrupt if the conditions for pro- cessing the interrupt have been satisfied. the wake-up feature is useful as a method of adding extra external pin interrupts. 12.2.1 input capture in cpu sleep mode cpu sleep mode allows input capture module opera- tion with reduced functionality. in the cpu sleep mode, the ici<1:0> bits are not applicable and the input cap- ture module can only function as an external interrupt source. the capture module must be configured for interrupt only on rising edge (icm<2:0> = 111 ) in order for the input capture module to be used while the device is in sleep mode. the prescale settings of 4:1 or 16:1 are not applicable in this mode. 12.2.2 input capture in cpu idle mode cpu idle mode allows input capture module operation with full functionality. in the cpu idle mode, the inter- rupt mode selected by the ici<1:0> bits is applicable, as well as the 4:1 and 16:1 capture prescale settings which are defined by control bits icm<2:0>. this mode requires the selected timer to be enabled. moreover, the icsidl bit must be asserted to a logic ? 0 ?. if the input capture module is defined as icm<2:0> = 111 in cpu idle mode, the input capture pin will serve only as an external interrupt pin. 12.3 input capture interrupts the input capture channels have the ability to generate an interrupt based upon the selected number of cap- ture events. the selection number is set by control bits ici<1:0> (icxcon<6:5>). each channel provides an interrupt flag (icxif) bit. the respective capture channel interrupt flag is located in the corresponding ifsx status register. enabling an interrupt is accomplished via the respec- tive capture channel interrupt enable (icxie) bit. the capture interrupt enable bit is located in the corresponding iec control register.
? 2006 microchip technology inc. ds70117f-page 85 dspic30f6011/6012/6013/6014 table 12-1: input capture register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state ic1buf 0140 input 1 capture register uuuu uuuu uuuu uuuu ic1con 0142 ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 ic2buf 0144 input 2 capture register uuuu uuuu uuuu uuuu ic2con 0146 ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 ic3buf 0148 input 3 capture register uuuu uuuu uuuu uuuu ic3con 014a ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 ic4buf 014c input 4 capture register uuuu uuuu uuuu uuuu ic4con 014e ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 ic5buf 0150 input 5 capture register uuuu uuuu uuuu uuuu ic5con 0152 ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 ic6buf 0154 input 6 capture register uuuu uuuu uuuu uuuu ic6con 0156 ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 ic7buf 0158 input 7 capture register uuuu uuuu uuuu uuuu ic7con 015a ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 ic8buf 015c input 8 capture register uuuu uuuu uuuu uuuu ic8con 015e ? ?icsidl ? ? ? ? ? ictmr ici<1:0> icov icbne icm<2:0> 0000 0000 0000 0000 legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 86 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 87 dspic30f6011/6012/6013/6014 13.0 output compare module this section describes the output compare module and associated operational modes. the features provided by this module are useful in applications requiring operational modes, such as: ? generation of variable width output pulses ? power factor correction figure 13-1 depicts a block diagram of the output compare module. the key operational features of the output compare module include: ? timer2 and timer3 selection mode ? simple output compare match mode ? dual output compare match mode ? simple pwm mode ? output compare during sleep and idle modes ? interrupt on output compare/pwm event these operating modes are determined by setting the appropriate bits in the 16-bit ocxcon sfr (where x = 1,2,3,...,n). the dspic dsc devices contain up to 8 compare channels (i.e., the maximum value of n is 8). ocxrs and ocxr in figure 13-1 represent the dual compare registers. in the dual compare mode, the ocxr register is used for the first compare and ocxrs is used for the second compare. figure 13-1: output compare mode block diagram note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). ocxr comparator output logic q s r ocm<2:0> output ocx set flag bit ocxif ocxrs mode select 3 note: where ?x? is shown, reference is made to the regi sters associated with the respective output compare channels 1 through n. ocfa octsel 01 t2p2_match tmr2<15:0 tmr3<15:0> t3p3_match from general purpose (for x = 1, 2, 3 or 4) or ocfb (for x = 5, 6, 7 or 8) 01 timer module enable
dspic30f6011/6012/6013/6014 ds70117f-page 88 ? 2006 microchip technology inc. 13.1 timer2 and timer3 selection mode each output compare channel can select between one of two 16-bit timers, timer2 or timer3. the selection of the timers is controlled by the octsel bit (ocxcon<3>). timer2 is the default timer resource for the output compare module. 13.2 simple output compare match mode when control bits ocm<2:0> (ocxcon<2:0>) = 001 , 010 or 011 , the selected output compare channel is configured for one of three simple output compare match modes: ? compare forces i/o pin low ? compare forces i/o pin high ? compare toggles i/o pin the ocxr register is used in these modes. the ocxr register is loaded with a value and is compared to the selected incrementing timer count. when a compare occurs, one of these compare match modes occurs. if the counter resets to zero before reaching the value in ocxr, the state of the ocx pin remains unchanged. 13.3 dual output compare match mode when control bits ocm<2:0> (ocxcon<2:0>) = 100 or 101 , the selected output compare channel is config- ured for one of two dual output compare modes, which are: ? single output pulse mode ? continuous output pulse mode 13.3.1 single pulse mode for the user to configure the module for the generation of a single output pulse, the following steps are required (assuming timer is off): ? determine instruction cycle time t cy . ? calculate desired pulse width value based on t cy . ? calculate time to start pulse from timer start value of 0x0000. ? write pulse width start and stop times into ocxr and ocxrs compare registers (x denotes channel 1, 2, ...,n). ? set timer period register to value equal to, or greater than value in ocxrs compare register. ? set ocm<2:0> = 100 . ? enable timer, ton (txcon<15>) = 1 . to initiate another single pulse, issue another write to set ocm<2:0> = 100 . 13.3.2 continuous pulse mode for the user to configure the module for the generation of a continuous stream of output pulses, the following steps are required: ? determine instruction cycle time t cy . ? calculate desired pulse value based on t cy . ? calculate timer to start pulse width from timer start value of 0x0000. ? write pulse width start and stop times into ocxr and ocxrs (x denotes channel 1, 2, ...,n) compare registers, respectively. ? set timer period register to value equal to, or greater than value in ocxrs compare register. ? set ocm<2:0> = 101 . ? enable timer, ton (txcon<15>) = 1 . 13.4 simple pwm mode when control bits ocm<2:0> (ocxcon<2:0>) = 110 or 111 , the selected output compare channel is config- ured for the pwm mode of operation. when configured for the pwm mode of operation, ocxr is the main latch (read only) and ocxrs is the secondary latch. this enables glitchless pwm transitions. the user must perform the following steps in order to configure the output compare module for pwm operation: 1. set the pwm period by writing to the appropriate period register. 2. set the pwm duty cycle by writing to the ocxrs register. 3. configure the output compare module for pwm operation. 4. set the tmrx prescale value and enable the timer, ton (txcon<15>) = 1 . 13.4.1 input pin fault protection for pwm when control bits ocm<2:0> (ocxcon<2:0>) = 111 , the selected output compare channel is again config- ured for the pwm mode of operation with the additional feature of input fault protection. while in this mode, if a logic ? 0 ? is detected on the ocfa/b pin, the respective pwm output pin is placed in the high impedance input state. the ocflt bit (ocxcon<4>) indicates whether a fault condition has occurred. this state will be main- tained until both of the following events have occurred: ? the external fault condition has been removed. ? the pwm mode has been re-enabled by writing to the appropriate control bits.
? 2006 microchip technology inc. ds70117f-page 89 dspic30f6011/6012/6013/6014 13.4.2 pwm period the pwm period is specified by writing to the prx register. the pwm period can be calculated using equation 13-1. equation 13-1: pwm frequency is defined as 1/[pwm period]. when the selected tmrx is equal to its respective period register, prx, the following four events occur on the next increment cycle: ? tmrx is cleared. ? the ocx pin is set. - exception 1: if pwm duty cycle is 0x0000, the ocx pin will remain low. - exception 2: if duty cycle is greater than prx, the pin will remain high. ? the pwm duty cycle is latched from ocxrs into ocxr. ? the corresponding timer interrupt flag is set. see figure 13-2 for key pwm period comparisons. timer3 is referred to in figure 13-2 for clarity. figure 13-2: pwm output timing 13.5 output compare operation during cpu sleep mode when the cpu enters sleep mode, all internal clocks are stopped. therefore, when the cpu enters the sleep state, the output compare channel will drive the pin to the active state that was observed prior to entering the cpu sleep state. for example, if the pin was high when the cpu entered the sleep state, the pin will remain high. likewise, if the pin was low when the cpu entered the sleep state, the pin will remain low. in either case, the output compare module will resume operation when the device wakes up. 13.6 output compare operation during cpu idle mode when the cpu enters the idle mode, the output compare module can operate with full functionality. the output compare channel will operate during the cpu idle mode if the ocsidl bit (ocxcon<13>) is at logic ? 0 ? and the selected time base (timer2 or timer3) is enabled and the tsidl bit of the selected timer is set to logic ? 0 ?. 13.7 output compare interrupts the output compare channels have the ability to gener- ate an interrupt on a compare match, for whichever match mode has been selected. for all modes except the pwm mode, when a compare event occurs, the respective interrupt flag (ocxif) is asserted and an interrupt will be generated if enabled. the ocxif bit is located in the corresponding ifs status register and must be cleared in software. the interrupt is enabled via the respective compare inter- rupt enable (ocxie) bit located in the corresponding iec control register. for the pwm mode, when an event occurs, the respec- tive timer interrupt flag (t2if or t3if) is asserted and an interrupt will be generated if enabled. the if bit is located in the ifs0 status register and must be cleared in software. the interrupt is enabled via the respective timer interrupt enable bit (t2ie or t3ie) located in the iec0 control register. the output compare interrupt flag is never set during the pwm mode of operation. pwm period = [(prx) + 1] ? 4 ? t osc ? (tmrx prescale value) period duty cycle tmr3 = duty cycle tmr3 = duty cycle tmr3 = pr3 t3if = 1 (interrupt flag) ocxr = ocxrs tmr3 = pr3 (interrupt flag) ocxr = ocxrs t3if = 1 (ocxr) (ocxr)
dspic30f6011/6012/6013/6014 ds70117f-page 90 ? 2006 microchip technology inc. table 13-1: output compare register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state oc1rs 0180 output compare 1 secondary register 0000 0000 0000 0000 oc1r 0182 output compare 1 main register 0000 0000 0000 0000 oc1con 0184 ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octsel ocm<2:0> 0000 0000 0000 0000 oc2rs 0186 output compare 2 secondary register 0000 0000 0000 0000 oc2r 0188 output compare 2 main register 0000 0000 0000 0000 oc2con 018a ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octse ocm<2:0> 0000 0000 0000 0000 oc3rs 018c output compare 3 secondary register 0000 0000 0000 0000 oc3r 018e output compare 3 main register 0000 0000 0000 0000 oc3con 0190 ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octsel ocm<2:0> 0000 0000 0000 0000 oc4rs 0192 output compare 4 secondary register 0000 0000 0000 0000 oc4r 0194 output compare 4 main register 0000 0000 0000 0000 oc4con 0196 ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octsel ocm<2:0> 0000 0000 0000 0000 oc5rs 0198 output compare 5 secondary register 0000 0000 0000 0000 oc5r 019a output compare 5 main register 0000 0000 0000 0000 oc5con 019c ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octsel ocm<2:0> 0000 0000 0000 0000 oc6rs 019e output compare 6 secondary register 0000 0000 0000 0000 oc6r 01a0 output compare 6 main register 0000 0000 0000 0000 oc6con 01a2 ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octsel ocm<2:0> 0000 0000 0000 0000 oc7rs 01a4 output compare 7 secondary register 0000 0000 0000 0000 oc7r 01a6 output compare 7 main register 0000 0000 0000 0000 oc7con 01a8 ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octsel ocm<2:0> 0000 0000 0000 0000 oc8rs 01aa output compare 8 secondary register 0000 0000 0000 0000 oc8r 01ac output compare 8 main register 0000 0000 0000 0000 oc8con 01ae ? ?ocsidl ? ? ? ? ? ? ? ? ocflt octsel ocm<2:0> 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 91 dspic30f6011/6012/6013/6014 14.0 spi module the serial peripheral interface (spi) module is a syn- chronous serial interface. it is useful for communicating with other peripheral devices, such as eeproms, shift registers, display drivers and a/d converters, or other microcontrollers. it is compatible with motorola's spi and siop interfaces. 14.1 operating function description each spi module consists of a 16-bit shift register, spixsr (where x = 1 or 2), used for shifting data in and out, and a buffer register, spixbuf. a control register, spixcon, configures the module. additionally, a status register, spixstat, indicates various status conditions. the serial interface consists of 4 pins: sdix (serial data input), sdox (serial data output), sckx (shift clock input or output), and ssx (active-low slave select). in master mode operation, sck is a clock output but in slave mode, it is a clock input. a series of eight (8) or sixteen (16) clock pulses shift out bits from the spixsr to sdox pin and simulta- neously shift in data from sdix pin. an interrupt is gen- erated when the transfer is complete and the corresponding interrupt flag bit (spi1if or spi2if) is set. this interrupt can be disabled through an interrupt enable bit (spi1ie or spi2ie). the receive operation is double-buffered. when a com- plete byte is received, it is transferred from spixsr to spixbuf. if the receive buffer is full when new data is being trans- ferred from spixsr to spixbuf, the module will set the spirov bit indicating an overflow condition. the trans- fer of the data from spixsr to spixbuf will not be completed and the new data will be lost. the module will not respond to scl transitions while spirov is ? 1 ?, effectively disabling the module until spixbuf is read by user software. transmit writes are also double-buffered. the user writes to spixbuf. when the master or slave transfer is completed, the contents of the shift register (spixsr) are moved to the receive buffer. if any transmit data has been written to the buffer register, the contents of the transmit buffer are moved to spixsr. the received data is thus placed in spixbuf and the transmit data in spixsr is ready for the next transfer. in master mode, the clock is generated by prescaling the system clock. data is transmitted as soon as a value is written to spixbuf. the interrupt is generated at the middle of the transfer of the last bit. in slave mode, data is transmitted and received as external clock pulses appear on sck. again, the inter- rupt is generated when the last bit is latched. if ssx control is enabled, then transmission and reception are enabled only when ssx = low. the sdox output will be disabled in ssx mode with ssx high. the clock provided to the module is (f osc /4). this clock is then prescaled by the primary (ppre<1:0>) and the secondary (spre<2:0>) prescale factors. the cke bit determines whether transmit occurs on transi- tion from active clock state to idle clock state, or vice versa. the ckp bit selects the idle state (high or low) for the clock. 14.1.1 word and byte communication a control bit, mode16 (spixcon<10>), allows the module to communicate in either 16-bit or 8-bit mode. 16-bit operation is identical to 8-bit operation except that the number of bits transmitted is 16 instead of 8. the user software must disable the module prior to changing the mode16 bit. the spi module is reset when the mode16 bit is changed by the user. a basic difference between 8-bit and 16-bit operation is that the data is transmitted out of bit 7 of the spixsr for 8-bit operation, and data is transmitted out of bit15 of the spixsr for 16-bit operation. in both modes, data is shifted into bit 0 of the spixsr. 14.1.2 sdox disable a control bit, dissdo, is provided to the spixcon reg- ister to allow the sdox output to be disabled. this will allow the spi module to be connected in an input only configuration. sdo can also be used for general purpose i/o. 14.2 framed spi support the module supports a basic framed spi protocol in master or slave mode. the control bit frmen enables framed spi support and causes the ssx pin to perform the frame synchronization pulse (fsync) function. the control bit spifsd determines whether the ssx pin is an input or an output (i.e., whether the module receives or generates the frame synchronization pulse). the frame pulse is an active high pulse for a single spi clock cycle. when frame synchronization is enabled, the data transmission starts only on the subsequent transmit edge of the spi clock. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). note: both the transmit buffer (spixtxb) and the receive buffer (spixrxb) are mapped to the same register address, spixbuf.
dspic30f6011/6012/6013/6014 ds70117f-page 92 ? 2006 microchip technology inc. figure 14-1: spi block diagram figure 14-2: spi master/slave connection note: x = 1 or 2. read write internal data bus sdix sdox ssx sckx spixsr spixbuf bit 0 shift clock edge select f cy primary 1, 4, 16, 64 enable master clock prescaler secondary prescaler 1:1-1:8 ss and fsync control clock control transmit spixbuf receive serial input buffer (spixbuf) shift register (spixsr) msb lsb sdox sdix processor 1 sckx spi master serial input buffer (spiybuf) shift register (spiysr) lsb msb sdiy sdoy processor 2 scky spi slave serial clock note: x = 1 or 2, y = 1 or 2.
? 2006 microchip technology inc. ds70117f-page 93 dspic30f6011/6012/6013/6014 14.3 slave select synchronization the ssx pin allows a synchronous slave mode. the spi must be configured in spi slave mode with ssx pin control enabled (ssen = 1 ). when the ssx pin is low, transmission and reception are enabled and the sdox pin is driven. when ssx pin goes high, the sdox pin is no longer driven. also, the spi module is re- synchronized, and all counters/control circuitry are reset. therefore, when the ssx pin is asserted low again, transmission/reception will begin at the msb even if ssx had been de-asserted in the middle of a transmit/receive. 14.4 spi operation during cpu sleep mode during sleep mode, the spi module is shutdown. if the cpu enters sleep mode while an spi transaction is in progress, then the transmission and reception is aborted. the transmitter and receiver will stop in sleep mode. however, register contents are not affected by entering or exiting sleep mode. 14.5 spi operation during cpu idle mode when the device enters idle mode, all clock sources remain functional. the spisidl bit (spixstat<13>) selects if the spi module will stop or continue on idle. if spisidl = 0 , the module will continue to operate when the cpu enters idle mode. if spisidl = 1 , the module will stop when the cpu enters idle mode.
dspic30f6011/6012/6013/6014 ds70117f-page 94 ? 2006 microchip technology inc. table 14-1: spi1 register map table 14-2: spi2 register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state spi1stat 0220 spien ? spisidl ? ? ? ? ? ? spirov ? ? ? ? spitbf spirbf 0000 0000 0000 0000 spi1con 0222 ? frmen spifsd ? dissdo mode16 smp cke ssen ckp msten spre2 spre1 spre0 ppre1 ppre0 0000 0000 0000 0000 spi1buf 0224 transmit and receive buffer 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state spi2stat 0226 spien ? spisidl ? ? ? ? ? ? spirov ? ? ? ? spitbf spirbf 0000 0000 0000 0000 spi2con 0228 ? frmen spifsd ? dissdo mode16 smp cke ssen ckp msten spre2 spre1 spre0 ppre1 ppre0 0000 0000 0000 0000 spi2buf 022a transmit and receive buffer 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 95 dspic30f6011/6012/6013/6014 15.0 i 2 c module the inter-integrated circuit (i 2 c tm ) module provides complete hardware support for both slave and multi- master modes of the i 2 c serial communication standard, with a 16-bit interface. this module offers the following key features: ?i 2 c interface supporting both master and slave operation. ?i 2 c slave mode supports 7 and 10-bit address. ?i 2 c master mode supports 7 and 10-bit address. ?i 2 c port allows bidirectional transfers between master and slaves. ? serial clock synchronization for i 2 c port can be used as a handshake mechanism to suspend and resume serial transfer (sclrel control). ?i 2 c supports multi-master operation; detects bus collision and will arbitrate accordingly. 15.1 operating function description the hardware fully implements all the master and slave functions of the i 2 c standard and fast mode specifications, as well as 7 and 10-bit addressing. thus, the i 2 c module can operate either as a slave or a master on an i 2 c bus. 15.1.1 various i 2 c modes the following types of i 2 c operation are supported: ?i 2 c slave operation with 7-bit address ?i 2 c slave operation with 10-bit address ?i 2 c master operation with 7 or 10-bit address see the i 2 c programmer?s model in figure 15-1. 15.1.2 pin configuration in i 2 c mode i 2 c has a 2-pin interface: the scl pin is clock and the sda pin is data. 15.1.3 i 2 c registers i2ccon and i2cstat are control and status registers, respectively. the i2ccon register is readable and writ- able. the lower 6 bits of i2cstat are read only. the remaining bits of the i2cstat are read/write. i2crsr is the shift register used for shifting data, whereas i2crcv is the buffer register to which data bytes are written, or from which data bytes are read. i2crcv is the receive buffer as shown in figure 15-1. i2ctrn is the transmit register to which bytes are written during a transmit operation, as shown in figure 15-2. the i2cadd register holds the slave address. a status bit, add10, indicates 10-bit address mode. the i2cbrg acts as the baud rate generator (brg) reload value. in receive operations, i2crsr and i2crcv together form a double-buffered receiver. when i2crsr receives a complete byte, it is transferred to i2crcv and an interrupt pulse is generated. during transmission, the i2ctrn is not double-buffered. figure 15-1: programmer?s model note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). note: following a restart condition in 10-bit mode, the user only needs to match the first 7-bit address. bit 7 bit 0 i2crcv (8 bits) bit 7 bit 0 i2ctrn (8 bits) bit 8 bit 0 i2cbrg (9 bits) bit 15 bit 0 i2ccon (16 bits) bit 15 bit 0 i2cstat (16 bits) bit 9 bit 0 i2cadd (10 bits)
dspic30f6011/6012/6013/6014 ds70117f-page 96 ? 2006 microchip technology inc. figure 15-2: i 2 c? block diagram i2crsr i2crcv internal data bus scl sda shift match detect i2cadd start and stop bit detect clock addr_match clock stretching i2ctrn lsb shift clock write read brg down i2cbrg reload control f cy start, restart, stop bit generate write read acknowledge generation collision detect write read write read i2ccon write read i2cstat control logic read lsb counter
? 2006 microchip technology inc. ds70117f-page 97 dspic30f6011/6012/6013/6014 15.2 i 2 c module addresses the i2cadd register contains the slave mode addresses. the register is a 10-bit register. if the a10m bit (i2ccon<10>) is ? 0 ?, the address is interpreted by the module as a 7-bit address. when an address is received, it is compared to the 7 lsbs of the i2cadd register. if the a10m bit is ? 1 ?, the address is assumed to be a 10-bit address. when an address is received, it will be compared with the binary value ? 11110 a9 a8 ? (where a9 and a8 are two most significant bits of i2cadd). if that value matches, the next address will be compared with the least significant 8 bits of i2cadd, as specified in the 10-bit addressing protocol. 15.3 i 2 c 7-bit slave mode operation once enabled (i2cen = 1 ), the slave module will wait for a start bit to occur (i.e., the i 2 c module is ?idle?). fol- lowing the detection of a start bit, 8 bits are shifted into i2crsr and the address is compared against i2cadd. in 7-bit mode (a10m = 0 ), bits i2cadd<6:0> are compared against i2crsr<7:1> and i2crsr<0> is the r_w bit. all incoming bits are sampled on the rising edge of scl. if an address match occurs, an acknowledgement will be sent, and the slave event interrupt flag (si2cif) is set on the falling edge of the ninth (ack ) bit. the address match does not affect the contents of the i2crcv buffer or the rbf bit. 15.3.1 slave transmission if the r_w bit received is a ? 1 ?, then the serial port will go into transmit mode. it will send ack on the ninth bit and then hold scl to ? 0 ? until the cpu responds by writ- ing to i2ctrn. scl is released by setting the sclrel bit, and 8 bits of data are shifted out. data bits are shifted out on the falling edge of scl, such that sda is valid during scl high. the interrupt pulse is sent on the falling edge of the ninth clock pulse, regardless of the status of the ack received from the master. 15.3.2 slave reception if the r_w bit received is a ? 0 ? during an address match, then receive mode is initiated. incoming bits are sampled on the rising edge of scl. after 8 bits are received, if i2crcv is not full or i2cov is not set, i2crsr is transferred to i2crcv. ack is sent on the ninth clock. if the rbf flag is set, indicating that i2crcv is still holding data from a previous operation (rbf = 1 ), then ack is not sent; however, the interrupt pulse is gener- ated. in the case of an overflow, the contents of the i2crsr are not loaded into the i2crcv. 15.4 i 2 c 10-bit slave mode operation in 10-bit mode, the basic receive and transmit opera- tions are the same as in the 7-bit mode. however, the criteria for address match is more complex. the i 2 c specification dictates that a slave must be addressed for a write operation with two address bytes following a start bit. the a10m bit is a control bit that signifies that the address in i2cadd is a 10-bit address rather than a 7-bit address. the address detection protocol for the first byte of a message address is identical for 7-bit and 10-bit messages, but the bits being compared are different. i2cadd holds the entire 10-bit address. upon receiv- ing an address following a start bit, i2crsr <7:3> is compared against a literal ? 11110 ? (the default 10-bit address) and i2crsr<2:1> are compared against i2cadd<9:8>. if a match occurs and if r_w = 0 , the interrupt pulse is sent. the add10 bit will be cleared to indicate a partial address match. if a match fails or r_w = 1 , the add10 bit is cleared and the module returns to the idle state. the low byte of the address is then received and com- pared with i2cadd<7:0>. if an address match occurs, the interrupt pulse is generated and the add10 bit is set, indicating a complete 10-bit address match. if an address match did not occur, the add10 bit is cleared and the module returns to the idle state. 15.4.1 10-bit mode slave transmission once a slave is addressed in this fashion with the full 10-bit address (we will refer to this state as ?prior_addr_match?), the master can begin sending data bytes for a slave reception operation. table 15-1: 7-bit i 2 c? slave addresses supported by dspic30f 0x00 general call address or start byte 0x01-0x03 reserved 0x04-0x07 hs mode master codes 0x08-0x77 valid 7-bit addresses 0x78-0x7b valid 10-bit addresses (lower 7 bits) 0x7c-0x7f reserved note: the i2crcv will be loaded if the i2cov bit = 1 and the rbf flag = 0 . in this case, a read of the i2crcv was performed but the user did not clear the state of the i2cov bit before the next receive occurred. the acknowledgement is not sent (ack = 1 ) and the i2crcv is updated.
dspic30f6011/6012/6013/6014 ds70117f-page 98 ? 2006 microchip technology inc. 15.4.2 10-bit mode slave reception once addressed, the master can generate a repeated start, reset the high byte of the address and set the r_w bit without generating a stop bit, thus initiating a slave transmit operation. 15.5 automatic clock stretch in the slave modes, the module can synchronize buffer reads and write to the master device by clock stretching. 15.5.1 transmit clock stretching both 10-bit and 7-bit transmit modes implement clock stretching by asserting the sclrel bit after the falling edge of the ninth clock, if the tbf bit is cleared, indicat- ing the buffer is empty. in slave transmit modes, clock stretching is always performed irrespective of the stren bit. clock synchronization takes place following the ninth clock of the transmit sequence. if the device samples an ack on the falling edge of the ninth clock and if the tbf bit is still clear, then the sclrel bit is automati- cally cleared. the sclrel being cleared to ? 0 ? will assert the scl line low. the user?s isr must set the sclrel bit before transmission is allowed to continue. by holding the scl line low, the user has time to ser- vice the isr and load the contents of the i2ctrn before the master device can initiate another transmit sequence. 15.5.2 receive clock stretching the stren bit in the i2ccon register can be used to enable clock stretching in slave receive mode. when the stren bit is set, the scl pin will be held low at the end of each data receive sequence. 15.5.3 clock stretching during 7-bit addressing (stren = 1 ) when the stren bit is set in slave receive mode, the scl line is held low when the buffer register is full. the method for stretching the scl output is the same for both 7 and 10-bit addressing modes. clock stretching takes place following the ninth clock of the receive sequence. on the falling edge of the ninth clock at the end of the ack sequence, if the rbf bit is set, the sclrel bit is automatically cleared, forcing the scl output to be held low. the user?s isr must set the sclrel bit before reception is allowed to continue. by holding the scl line low, the user has time to ser- vice the isr and read the contents of the i 2 crcv before the master device can initiate another receive sequence. this will prevent buffer overruns from occurring. 15.5.4 clock stretching during 10-bit addressing (stren = 1 ) clock stretching takes place automatically during the addressing sequence. because this module has a register for the entire address, it is not necessary for the protocol to wait for the address to be updated. after the address phase is complete, clock stretching will occur on each data receive or transmit sequence as was described earlier. 15.6 software controlled clock stretching (stren = 1 ) when the stren bit is ? 1 ?, the sclrel bit may be cleared by software to allow software to control the clock stretching. the logic will synchronize writes to the sclrel bit with the scl clock. clearing the sclrel bit will not assert the scl output until the module detects a falling edge on the scl output and scl is sampled low. if the sclrel bit is cleared by the user while the scl line has been sampled low, the scl out- put will be asserted (held low). the scl output will remain low until the sclrel bit is set, and all other devices on the i 2 c bus have de-asserted scl. this ensures that a write to the sclrel bit will not violate the minimum high time requirement for scl. if the stren bit is ? 0 ?, a software write to the sclrel bit will be disregarded and have no effect on the sclrel bit. 15.7 interrupts the i 2 c module generates two interrupt flags, mi2cif (i 2 c master interrupt flag) and si2cif (i 2 c slave inter- rupt flag). the mi2cif interrupt flag is activated on completion of a master message event. the si2cif interrupt flag is activated on detection of a message directed to the slave. note 1: if the user loads the contents of i2ctrn, setting the tbf bit before the falling edge of the ninth clock, the sclrel bit will not be cleared and clock stretching will not occur. 2: the sclrel bit can be set in software, regardless of the state of the tbf bit. note 1: if the user reads the contents of the i2crcv, clearing the rbf bit before the falling edge of the ninth clock, the sclrel bit will not be cleared and clock stretching will not occur. 2: the sclrel bit can be set in software regardless of the state of the rbf bit. the user should be careful to clear the rbf bit in the isr before the next receive sequence in order to prevent an overflow condition.
? 2006 microchip technology inc. ds70117f-page 99 dspic30f6011/6012/6013/6014 15.8 slope control the i 2 c standard requires slope control on the sda and scl signals for fast mode (400 khz). the control bit, disslw, enables the user to disable slew rate con- trol if desired. it is necessary to disable the slew rate control for 1 mhz mode. 15.9 ipmi support the control bit, ipmien, enables the module to support intelligent peripheral management interface (ipmi). when this bit is set, the module accepts and acts upon all addresses. 15.10 general call address support the general call address can address all devices. when this address is used, all devices should, in theory, respond with an acknowledgement. the general call address is one of eight addresses reserved for specific purposes by the i 2 c protocol. it consists of all ? 0 ?s with r_w = 0 . the general call address is recognized when the gen- eral call enable (gcen) bit is set (i2ccon<7> = 1 ). following a start bit detection, 8 bits are shifted into i2crsr and the address is compared with i2cadd, and is also compared with the general call address which is fixed in hardware. if a general call address match occurs, the i2crsr is transferred to the i2crcv after the eighth clock, the rbf flag is set and on the falling edge of the ninth bit (ack bit), the master event interrupt flag (mi2cif) is set. when the interrupt is serviced, the source for the inter- rupt can be checked by reading the contents of the i2crcv to determine if the address was device specific or a general call address. 15.11 i 2 c master support as a master device, six operations are supported: ? assert a start condition on sda and scl. ? assert a restart condition on sda and scl. ? write to the i2ctrn register initiating transmission of data/address. ? generate a stop condition on sda and scl. ? configure the i 2 c port to receive data. ? generate an ack condition at the end of a received byte of data. 15.12 i 2 c master operation the master device generates all of the serial clock pulses and the start and stop conditions. a transfer is ended with a stop condition or with a repeated start condition. since the repeated start condition is also the beginning of the next serial transfer, the i 2 c bus will not be released. in master transmitter mode, serial data is output through sda, while scl outputs the serial clock. the first byte transmitted contains the slave address of the receiving device (7 bits) and the data direction bit. in this case, the data direction bit (r_w) is logic ? 0 ?. serial data is transmitted 8 bits at a time. after each byte is transmitted, an ack bit is received. start and stop con- ditions are output to indicate the beginning and the end of a serial transfer. in master receive mode, the first byte transmitted con- tains the slave address of the transmitting device (7 bits) and the data direction bit. in this case, the data direction bit (r_w) is logic ? 1 ?. thus, the first byte trans- mitted is a 7-bit slave address, followed by a ? 1 ? to indi- cate receive bit. serial data is received via sda while scl outputs the serial clock. serial data is received 8 bits at a time. after each byte is received, an ack bit is transmitted. start and stop conditions indicate the beginning and end of transmission. 15.12.1 i 2 c master transmission transmission of a data byte, a 7-bit address, or the sec- ond half of a 10-bit address is accomplished by simply writing a value to i2ctrn register. the user should only write to i2ctrn when the module is in a wait state. this action will set the buffer full flag (tbf) and allow the baud rate generator to begin counting and start the next transmission. each bit of address/data will be shifted out onto the sda pin after the falling edge of scl is asserted. the transmit status flag, trstat (i2cstat<14>), indicates that a master transmit is in progress. 15.12.2 i 2 c master reception master mode reception is enabled by programming the receive enable bit, rcen (i2ccon<3>). the i 2 c module must be idle before the rcen bit is set, other- wise the rcen bit will be disregarded. the baud rate generator begins counting and on each rollover, the state of the scl pin ack and data are shifted into the i2crsr on the rising edge of each clock.
dspic30f6011/6012/6013/6014 ds70117f-page 100 ? 2006 microchip technology inc. 15.12.3 baud rate generator in i 2 c master mode, the reload value for the brg is located in the i2cbrg register. when the brg is loaded with this value, the brg counts down to ? 0 ? and stops until another reload has taken place. if clock arbi- tration is taking place, for instance, the brg is reloaded when the scl pin is sampled high. as per the i 2 c standard, f sck may be 100 khz or 400 khz. however, the user can specify any baud rate up to 1 mhz. i2cbrg values of ? 0 ? or ? 1 ? are illegal. equation 15-1: serial clock rate 15.12.4 clock arbitration clock arbitration occurs when the master de-asserts the scl pin (scl allowed to float high) during any receive, transmit, or restart/stop condition. when the scl pin is allowed to float high, the baud rate gener- ator is suspended from counting until the scl pin is actually sampled high. when the scl pin is sampled high, the baud rate generator is reloaded with the contents of i2cbrg and begins counting. this ensures that the scl high time will always be at least one brg rollover count in the event that the clock is held low by an external device. 15.12.5 multi-master communication, bus collision, and bus arbitration multi-master operation support is achieved by bus arbi- tration. when the master outputs address/data bits onto the sda pin, arbitration takes place when the master outputs a ? 1 ? on sda by letting sda float high while another master asserts a ? 0 ?. when the scl pin floats high, data should be stable. if the expected data on sda is a ? 1 ? and the data sampled on the sda pin = 0 , then a bus collision has taken place. the master will set the mi2cif pulse and reset the master portion of the i 2 c port to its idle state. if a transmit was in progress when the bus collision occurred, the transmission is halted, the tbf flag is cleared, the sda and scl lines are de-asserted and a value can now be written to i2ctrn. when the user services the i 2 c master event interrupt service rou- tine, if the i 2 c bus is free (i.e., the p bit is set), the user can resume communication by asserting a start condition. if a start, restart, stop or acknowledge condition was in progress when the bus collision occurred, the condi- tion is aborted, the sda and scl lines are de-asserted, and the respective control bits in the i2ccon register are cleared to ? 0 ?. when the user services the bus col- lision interrupt service routine, and if the i 2 c bus is free, the user can resume communication by asserting a start condition. the master will continue to monitor the sda and scl pins, and if a stop condition occurs, the mi2cif bit will be set. a write to the i2ctrn will start the transmission of data at the first data bit regardless of where the transmitter left off when bus collision occurred. in a multi-master environment, the interrupt generation on the detection of start and stop conditions allows the determination of when the bus is free. control of the i 2 c bus can be taken when the p bit is set in the i2cstat register, or the bus is idle and the s and p bits are cleared. 15.13 i 2 c module operation during cpu sleep and idle modes 15.13.1 i 2 c operation during cpu sleep mode when the device enters sleep mode, all clock sources to the module are shutdown and stay at logic ? 0 ?. if sleep occurs in the middle of a transmission and the state machine is partially into a transmission as the clocks stop, then the transmission is aborted. similarly, if sleep occurs in the middle of a reception, then the reception is aborted. 15.13.2 i 2 c operation during cpu idle mode for the i 2 c, the i2csidl bit selects if the module will stop on idle or continue on idle. if i2csidl = 0 , the module will continue operation on assertion of the idle mode. if i2csidl = 1 , the module will stop on idle. i2cbrg = f cy f cy f sck 1,111,111 ? 1 ? ()
? 2006 microchip technology inc. ds70117f-page 101 dspic30f6011/6012/6013/6014 table 15-2: i 2 c register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state i2crcv 0200 ? ? ? ? ? ? ? ? receive register 0000 0000 0000 0000 i2ctrn 0202 ? ? ? ? ? ? ? ? transmit register 0000 0000 1111 1111 i2cbrg 0204 ? ? ? ? ? ? ? baud rate generator 0000 0000 0000 0000 i2ccon 0206 i2cen ? i2csidl sclrel ipmien a10m disslw smen gcen stren ackdt acken rcen pen rsen sen 0001 0000 0000 0000 i2cstat 0208 ackstat trstat ? ? ? bcl gcstat add10 iwcol i2cov d_a p s r_w rbf tbf 0000 0000 0000 0000 i2cadd 020a ? ? ? ? ? ? address register 0000 0000 0000 0000 note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 102 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 103 dspic30f6011/6012/6013/6014 16.0 universal asynchronous receiver transmitter (uart) module this section describes the universal asynchronous receiver/transmitter communications module. 16.1 uart module overview the key features of the uart module are: ? full-duplex, 8 or 9-bit data communication ? even, odd or no parity options (for 8-bit data) ? one or two stop bits ? fully integrated baud rate generator with 16-bit prescaler ? baud rates range from 38 bps to 1.875 mbps at a 30 mhz instruction rate ? 4-word deep transmit data buffer ? 4-word deep receive data buffer ? parity, framing and buffer overrun error detection ? support for interrupt only on address detect (9th bit = 1 ) ? separate transmit and receive interrupts ? loopback mode for diagnostic support figure 16-1: uart transmitter block diagram note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). write write utx8 uxtxreg low byte load tsr transmit control ? control tsr ? control buffer ? generate flags ? generate interrupt control and status bits uxtxif data ? 0 ? (start) ? 1 ? (stop) parity parity generator transmit shift register (uxtsr) 16 divider control signals 16x baud clock from baud rate generator internal data bus utxbrk uxtx note: x = 1 or 2.
dspic30f6011/6012/6013/6014 ds70117f-page 104 ? 2006 microchip technology inc. figure 16-2: uart receiver block diagram read urx8 uxrxreg low byte load rsr uxmode receive buffer control ? generate flags ? generate interrupt uxrxif uxrx start bit detect receive shift register 16 divider control signals uxsta ? shift data characters read read write write to buffer 8-9 (uxrsr) perr ferr parity check stop bit detect shift clock generation wake logic 16 internal data bus 1 0 lpback from uxtx 16x baud clock from baud rate generator
? 2006 microchip technology inc. ds70117f-page 105 dspic30f6011/6012/6013/6014 16.2 enabling and setting up uart 16.2.1 enabling the uart the uart module is enabled by setting the uarten bit in the uxmode register (where x = 1 or 2). once enabled, the uxtx and uxrx pins are configured as an output and an input respectively, overriding the tris and latch register bit settings for the corresponding i/o port pins. the uxtx pin is at logic ? 1 ? when no transmission is taking place. 16.2.2 disabling the uart the uart module is disabled by clearing the uarten bit in the uxmode register. this is the default state after any reset. if the uart is disabled, all i/o pins operate as port pins under the control of the latch and tris bits of the corresponding port pins. disabling the uart module resets the buffers to empty states. any data characters in the buffers are lost and the baud rate counter is reset. all error and status flags associated with the uart module are reset when the module is disabled. the urxda, oerr, ferr, perr, utxen, utxbrk and utxbf bits are cleared, whereas ridle and trmt are set. other control bits, including adden, urxisel<1:0>, utxisel, as well as the uxmode and uxbrg registers, are not affected. clearing the uarten bit while the uart is active will abort all pending transmissions and receptions and reset the module as defined above. re-enabling the uart will restart the uart in the same configuration. 16.2.3 setting up data, parity and stop bit selections control bits pdsel<1:0> in the uxmode register are used to select the data length and parity used in the transmission. the data length may either be 8 bits with even, odd or no parity, or 9 bits with no parity. the stsel bit determines whether one or two stop bits will be used during data transmission. the default (power-on) setting of the uart is 8 bits, no parity and 1 stop bit (typically represented as 8, n, 1). 16.3 transmitting data 16.3.1 transmitting in 8-bit data mode the following steps must be performed in order to transmit 8-bit data: 1. set up the uart: first, the data length, parity and number of stop bits must be selected. then, the transmit and receive interrupt enable and priority bits are setup in the uxmode and uxsta registers. also, the appropriate baud rate value must be written to the uxbrg register. 2. enable the uart by setting the uarten bit (uxmode<15>). 3. set the utxen bit (uxsta<10>), thereby enabling a transmission. 4. write the byte to be transmitted to the lower byte of uxtxreg. the value will be transferred to the transmit shift register (uxtsr) immediately and the serial bit stream will start shifting out during the next rising edge of the baud clock. alternatively, the data byte may be written while utxen = 0 , following which, the user may set utxen. this will cause the serial bit stream to begin immediately because the baud clock will start from a cleared state. 5. a transmit interrupt will be generated, depend- ing on the value of the interrupt control bit utxisel (uxsta<15>). 16.3.2 transmitting in 9-bit data mode the sequence of steps involved in the transmission of 9-bit data is similar to 8-bit transmission, except that a 16-bit data word (of which the upper 7 bits are always clear) must be written to the uxtxreg register. 16.3.3 transmit buffer (u x txb) the transmit buffer is 9 bits wide and 4 characters deep. including the transmit shift register (uxtsr), the user effectively has a 5-deep fifo (first-in, first- out) buffer. the utxbf status bit (uxsta<9>) indicates whether the transmit buffer is full. if a user attempts to write to a full buffer, the new data will not be accepted into the fifo, and no data shift will occur within the buffer. this enables recovery from a buffer overrun condition. the fifo is reset during any device reset but is not affected when the device enters or wakes up from a power-saving mode.
dspic30f6011/6012/6013/6014 ds70117f-page 106 ? 2006 microchip technology inc. 16.3.4 transmit interrupt the transmit interrupt flag (u1txif or u2txif) is located in the corresponding interrupt flag register. the transmitter generates an edge to set the uxtxif bit. the condition for generating the interrupt depends on the utxisel control bit: a) if utxisel = 0 , an interrupt is generated when a word is transferred from the transmit buffer to the transmit shift register (uxtsr). this implies that the transmit buffer has at least one empty word. b) if utxisel = 1 , an interrupt is generated when a word is transferred from the transmit buffer to the transmit shift register (uxtsr) and the transmit buffer is empty. switching between the two interrupt modes during operation is possible and sometimes offers more flexibility. 16.3.5 transmit break setting the utxbrk bit (uxsta<11>) will cause the uxtx line to be driven to logic ? 0 ?. the utxbrk bit overrides all transmission activity. therefore, the user should generally wait for the transmitter to be idle before setting utxbrk. to send a break character, the utxbrk bit must be set by software and must remain set for a minimum of 13 baud clock cycles. the utxbrk bit is then cleared by software to generate stop bits. the user must wait for a duration of at least one or two baud clock cycles in order to ensure a valid stop bit(s) before reloading the uxtxb, or starting other transmitter activity. transmis- sion of a break character does not generate a transmit interrupt. 16.4 receiving data 16.4.1 receiving in 8-bit or 9-bit data mode the following steps must be performed while receiving 8-bit or 9-bit data: 1. set up the uart (see section 16.3.1 ?trans- mitting in 8-bit data mode? ). 2. enable the uart (see section 16.3.1 ?trans- mitting in 8-bit data mode? ). 3. a receive interrupt will be generated when one or more data words have been received, depending on the receive interrupt settings specified by the urxisel bits (uxsta<7:6>). 4. read the oerr bit to determine if an overrun error has occurred. the oerr bit must be reset in software. 5. read the received data from uxrxreg. the act of reading uxrxreg will move the next word to the top of the receive fifo, and the perr and ferr values will be updated. 16.4.2 receive buffer (u x rxb) the receive buffer is 4 words deep. including the receive shift register (uxrsr), the user effectively has a 5-word deep fifo buffer. urxda (uxsta<0>) = 1 indicates that the receive buffer has data available. urxda = 0 implies that the buffer is empty. if a user attempts to read an empty buffer, the old values in the buffer will be read and no data shift will occur within the fifo. the fifo is reset during any device reset. it is not affected when the device enters or wakes up from a power-saving mode. 16.4.3 receive interrupt the receive interrupt flag (u1rxif or u2rxif) can be read from the corresponding interrupt flag register. the interrupt flag is set by an edge generated by the receiver. the condition for setting the receive interrupt flag depends on the settings specified by the urxisel<1:0> (uxsta<7:6>) control bits. a) if urxisel<1:0> = 00 or 01 , an interrupt is gen- erated every time a data word is transferred from the receive shift register (uxrsr) to the receive buffer. there may be one or more characters in the receive buffer. b) if urxisel<1:0> = 10 , an interrupt is generated when a word is transferred from the receive shift register (uxrsr) to the receive buffer, which as a result of the transfer, contains 3 characters. c) if urxisel<1:0> = 11 , an interrupt is set when a word is transferred from the receive shift reg- ister (uxrsr) to the receive buffer, which as a result of the transfer, contains 4 characters (i.e., becomes full). switching between the interrupt modes during opera- tion is possible, though generally not advisable during normal operation. 16.5 reception error handling 16.5.1 receive buffer overrun error (oerr bit) the oerr bit (uxsta<1>) is set if all of the following conditions occur: a) the receive buffer is full. b) the receive shift register is full, but unable to transfer the character to the receive buffer. c) the stop bit of the character in the uxrsr is detected, indicating that the uxrsr needs to transfer the character to the buffer.
? 2006 microchip technology inc. ds70117f-page 107 dspic30f6011/6012/6013/6014 once oerr is set, no further data is shifted in uxrsr (until the oerr bit is cleared in software or a reset occurs). the data held in uxrsr and uxrxreg remains valid. 16.5.2 framing error (ferr) the ferr bit (uxsta<2>) is set if a ? 0 ? is detected instead of a stop bit. if two stop bits are selected, both stop bits must be ? 1 ?, otherwise ferr will be set. the read only ferr bit is buffered along with the received data. it is cleared on any reset. 16.5.3 parity error (perr) the perr bit (uxsta<3>) is set if the parity of the received word is incorrect. this error bit is applicable only if a parity mode (odd or even) is selected. the read only perr bit is buffered along with the received data bytes. it is cleared on any reset. 16.5.4 idle status when the receiver is active (i.e., between the initial detection of the start bit and the completion of the stop bit), the ridle bit (uxsta<4>) is ? 0 ?. between the com- pletion of the stop bit and detection of the next start bit, the ridle bit is ? 1 ?, indicating that the uart is idle. 16.5.5 receive break the receiver will count and expect a certain number of bit times based on the values programmed in the pdsel (uxmode<2:1>) and stsel (uxmode<0>) bits. if the break is longer than 13 bit times, the reception is considered complete after the number of bit times specified by pdsel and stsel. the urxda bit is set, ferr is set, zeros are loaded into the receive fifo, interrupts are generated if appropriate and the ridle bit is set. when the module receives a long break signal and the receiver has detected the start bit, the data bits and the invalid stop bit (which sets the ferr), the receiver must wait for a valid stop bit before looking for the next start bit. it cannot assume that the break condition on the line is the next start bit. break is regarded as a character containing all ? 0 ?s with the ferr bit set. the break character is loaded into the buffer. no further reception can occur until a stop bit is received. note that ridle goes high when the stop bit has not yet been received. 16.6 address detect mode setting the adden bit (uxsta<5>) enables this spe- cial mode in which a 9th bit (urx8) value of ? 1 ? identi- fies the received word as an address, rather than data. this mode is only applicable for 9-bit data communica- tion. the urxisel control bit does not have any impact on interrupt generation in this mode since an interrupt (if enabled) will be generated every time the received word has the 9th bit set. 16.7 loopback mode setting the lpback bit enables this special mode in which the uxtx pin is internally connected to the uxrx pin. when configured for the loopback mode, the uxrx pin is disconnected from the internal uart receive logic. however, the uxtx pin still functions as in a normal operation. to select this mode: a) configure uart for desired mode of operation. b) set lpback = 1 to enable loopback mode. c) enable transmission as defined in section 16.3 ?transmitting data? . 16.8 baud rate generator the uart has a 16-bit baud rate generator to allow maximum flexibility in baud rate generation. the baud rate generator register (uxbrg) is readable and writable. the baud rate is computed as follows: brg = 16-bit value held in uxbrg register (0 through 65535) f cy = instruction clock rate (1/t cy ) the baud rate is given by equation 16-1. equation 16-1: baud rate therefore, the maximum baud rate possible is f cy /16 (if brg = 0 ), and the minimum baud rate possible is f cy /(16 * 65536). with a full 16-bit baud rate generator at 30 mips operation, the minimum baud rate achievable is 28.5 bps. baud rate = f cy /(16 * (brg + 1))
dspic30f6011/6012/6013/6014 ds70117f-page 108 ? 2006 microchip technology inc. 16.9 auto baud support to allow the system to determine baud rates of received characters, the input can be optionally linked to a capture input (ic1 for uart1, ic2 for uart2). to enable this mode, the user must program the input cap- ture module to detect the falling and rising edges of the start bit. 16.10 uart operation during cpu sleep and idle modes 16.10.1 uart operation during cpu sleep mode when the device enters sleep mode, all clock sources to the module are shutdown and stay at logic ? 0 ?. if entry into sleep mode occurs while a transmission is in progress, then the transmission is aborted. the uxtx pin is driven to logic ? 1 ?. similarly, if entry into sleep mode occurs while a reception is in progress, then the reception is aborted. the uxsta, uxmode, transmit and receive registers and buffers, and the uxbrg register are not affected by sleep mode. if the wake bit (uxmode<7>) is set before the device enters sleep mode, then a falling edge on the uxrx pin will generate a receive interrupt. the receive interrupt select mode bit (urxisel) has no effect for this func- tion. if the receive interrupt is enabled, then this will wake-up the device from sleep. the uarten bit must be set in order to generate a wake-up interrupt. 16.10.2 uart operation during cpu idle mode for the uart, the usidl bit selects if the module will stop operation when the device enters idle mode or whether the module will continue on idle. if usidl = 0 , the module will continue operation during idle mode. if usidl = 1 , the module will stop on idle.
? 2006 microchip technology inc. ds70117f-page 109 dspic30f6011/6012/6013/6014 table 16-1: uart1 register map table 16-2: uart2 register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state u1mode 020c uarten ?usidl ? ? ? ? ? wake lpback abaud ? ? pdsel1 pdsel0 stsel 0000 0000 0000 0000 u1sta 020e utxisel ? ? ? utxbrk utxen utxbf trmt urxisel1 urxisel0 adden ridle perr ferr oerr urxda 0000 0001 0001 0000 u1txreg 0210 ? ? ? ? ? ? ? utx8 transmit register 0000 000u uuuu uuuu u1rxreg 0212 ? ? ? ? ? ? ? urx8 receive register 0000 0000 0000 0000 u1brg 0214 baud rate generator prescaler 0000 0000 0000 0000 legend: u = uninitialized bit note: refer to ?dspic30f family reference manual? (ds70046) for descriptions of register bit fields. sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state u2mode 0216 uarten ?usidl ? ? ? ? ? wake lpback abaud ? ? pdsel1 pdsel0 stsel 0000 0000 0000 0000 u2sta 0218 utxisel ? ? ? utxbrk utxen utxbf trmt urxisel1 urxisel0 adden ridle perr ferr oerr urxda 0000 0001 0001 0000 u2txreg 021a ? ? ? ? ? ? ? utx8 transmit register 0000 000u uuuu uuuu u2rxreg 021c ? ? ? ? ? ? ? urx8 receive register 0000 0000 0000 0000 u2brg 021e baud rate generator prescaler 0000 0000 0000 0000 legend: u = uninitialized bit note: refer to ?dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 110 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 111 dspic30f6011/6012/6013/6014 17.0 can module 17.1 overview the controller area network (can) module is a serial interface, useful for communicating with other can modules or microcontroller devices. this interface/ protocol was designed to allow communications within noisy environments. the can module is a communication controller imple- menting the can 2.0 a/b protocol, as defined in the bosch specification. the module will support can 1.2, can 2.0a, can 2.0b passive, and can 2.0b active versions of the protocol. the module implemen- tation is a full can system. the can specification is not covered within this data sheet. the reader may refer to the bosch can specification for further details. the module features are as follows: ? implementation of the can protocol can 1.2, can 2.0a and can 2.0b ? standard and extended data frames ? 0-8 bytes data length ? programmable bit rate up to 1 mbit/sec ? support for remote frames ? double-buffered receiver with two prioritized received message storage buffers (each buffer may contain up to 8 bytes of data) ? 6 full (standard/extended identifier) acceptance filters, 2 associated with the high priority receive buffer and 4 associated with the low priority receive buffer ? 2 full acceptance filter masks, one each associated with the high and low priority receive buffers ? three transmit buffers with application specified prioritization and abort capability (each buffer may contain up to 8 bytes of data) ? programmable wake-up functionality with integrated low-pass filter ? programmable loopback mode supports self-test operation ? signaling via interrupt capabilities for all can receiver and transmitter error states ? programmable clock source ? programmable link to input capture module (ic2, for both can1 and can2) for time-stamping and network synchronization ? low-power sleep and idle mode the can bus module consists of a protocol engine and message buffering/control. the can protocol engine handles all functions for receiving and transmitting messages on the can bus. messages are transmitted by first loading the appropriate data registers. status and errors can be checked by reading the appropriate registers. any message detected on the can bus is checked for errors and then matched against filters to see if it should be received and stored in one of the receive registers. 17.2 frame types the can module transmits various types of frames which include data messages or remote transmission requests initiated by the user, as other frames that are automatically generated for control purposes. the following frame types are supported: ? standard data frame: a standard data frame is generated by a node when the node wishes to transmit data. it includes an 11-bit standard identifier (sid) but not an 18-bit extended identifier (eid). ? extended data frame: an extended data frame is similar to a standard data frame but includes an extended identifier as well. ? remote frame: it is possible for a destination node to request the data from the source. for this purpose, the desti- nation node sends a remote frame with an identi- fier that matches the identifier of the required data frame. the appropriate data source node will then send a data frame as a response to this remote request. ? error frame: an error frame is generated by any node that detects a bus error. an error frame consists of 2 fields: an error flag field and an error delimiter field. ? overload frame: an overload frame can be generated by a node as a result of 2 conditions. first, the node detects a dominant bit during interframe space which is an illegal condition. second, due to internal condi- tions, the node is not yet able to start reception of the next message. a node may generate a maxi- mum of 2 sequential overload frames to delay the start of the next message. ? interframe space: interframe space separates a proceeding frame (of whatever type) from a following data or remote frame. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046).
dspic30f6011/6012/6013/6014 ds70117f-page 112 ? 2006 microchip technology inc. figure 17-1: can buffers and protocol engine block diagram acceptance filter rxf2 r x b 1 a c c e p t a c c e p t identifier data field data field identifier acceptance mask rxm1 acceptance filter rxf3 acceptance filter rxf4 acceptance filter rxf5 m a b acceptance mask rxm0 acceptance filter rxf0 acceptance filter rxf1 r x b 0 msgreq txb2 txabt txlarb txerr mtxbuff message message queue control transmit byte sequencer msgreq txb1 txabt txlarb txerr mtxbuff message msgreq txb0 txabt txlarb txerr mtxbuff message receive shift transmit shift receive error transmit error protocol rerrcnt terrcnt err pas bus off finite state machine counter counter transmit logic bit timing logic citx (1) cirx (1) bit timing generator protocol engine buffers crc check crc generator note 1: i = 1 or 2 refers to a particular can module (can1 or can2).
? 2006 microchip technology inc. ds70117f-page 113 dspic30f6011/6012/6013/6014 17.3 modes of operation the can module can operate in one of several operation modes selected by the user. these modes include: ? initialization mode ? disable mode ? normal operation mode ? listen only mode ? loopback mode ? error recognition mode modes are requested by setting the reqop<2:0> bits (cictrl<10:8>). entry into a mode is acknowledged by monitoring the opmode<2:0> bits (cictrl<7:5>). the module will not change the mode and the opmode bits until a change in mode is acceptable, generally during bus idle time which is defined as at least 11 consecutive recessive bits. 17.3.1 initialization mode in the initialization mode, the module will not transmit or receive. the error counters are cleared and the inter- rupt flags remain unchanged. the programmer will have access to configuration registers that are access restricted in other modes. the module will protect the user from accidentally violating the can protocol through programming errors. all registers which control the configuration of the module can not be modified while the module is on-line. the can module will not be allowed to enter the configuration mode while a transmission is taking place. the configuration mode serves as a lock to protect the following registers. ? all module control registers ? baud rate and interrupt configuration registers ? bus timing registers ? identifier acceptance filter registers ? identifier acceptance mask registers 17.3.2 disable mode in disable mode, the module will not transmit or receive. the module has the ability to set the wakif bit due to bus activity, however, any pending interrupts will remain and the error counters will retain their value. if the reqop<2:0> bits (cictrl<10:8>) = 001 , the module will enter the module disable mode. if the module is active, the module will wait for 11 recessive bits on the can bus, detect that condition as an idle bus, then accept the module disable command. when the opmode<2:0> bits (cictrl<7:5>) = 001 , that indi- cates whether the module successfully went into module disable mode. the i/o pins will revert to normal i/o function when the module is in the module disable mode. the module can be programmed to apply a low-pass filter function to the cirx input line while the module or the cpu is in sleep mode. the wakfil bit (cicfg2<14>) enables or disables the filter. 17.3.3 normal operation mode normal operating mode is selected when reqop<2:0> = 000 . in this mode, the module is acti- vated and the i/o pins will assume the can bus func- tions. the module will transmit and receive can bus messages via the cxtx and cxrx pins. 17.3.4 listen only mode if the listen only mode is activated, the module on the can bus is passive. the transmitter buffers revert to the port i/o function. the receive pins remain inputs. for the receiver, no error flags or acknowledge signals are sent. the error counters are deactivated in this state. the listen only mode can be used for detecting the baud rate on the can bus. to use this, it is neces- sary that there are at least two further nodes that communicate with each other. 17.3.5 listen all messages mode the module can be set to ignore all errors and receive any message. the error recognition mode is activated by setting reqop<2:0> = ? 111 ?. in this mode, the data which is in the message assembly buffer until the time an error occurred, is copied in the receive buffer and can be read via the cpu interface. 17.3.6 loopback mode if the loopback mode is activated, the module will con- nect the internal transmit signal to the internal receive signal at the module boundary. the transmit and receive pins revert to their port i/o function. note: typically, if the can module is allowed to transmit in a particular mode of operation and a transmission is requested immedi- ately after the can module has been placed in that mode of operation, the mod- ule waits for 11 consecutive recessive bits on the bus before starting transmission. if the user switches to disable mode within this 11-bit period, then this transmission is aborted and the corresponding txabt bit is set and txreq bit is cleared.
dspic30f6011/6012/6013/6014 ds70117f-page 114 ? 2006 microchip technology inc. 17.4 message reception 17.4.1 receive buffers the can bus module has 3 receive buffers. however, one of the receive buffers is always committed to mon- itoring the bus for incoming messages. this buffer is called the message assembly buffer (mab). so there are 2 receive buffers visible, rxb0 and rxb1, that can essentially instantaneously receive a complete message from the protocol engine. all messages are assembled by the mab and are trans- ferred to the rxbn buffers only if the acceptance filter criterion are met. when a message is received, the rxnif flag (ciintf<0> or ciinrf<1>) will be set. this bit can only be set by the module when a message is received. the bit is cleared by the cpu when it has com- pleted processing the message in the buffer. if the rxnie bit (ciinte<0> or ciinte<1>) is set, an interrupt will be generated when a message is received. rxf0 and rxf1 filters with rxm0 mask are associated with rxb0. the filters rxf2, rxf3, rxf4, and rxf5 and the mask rxm1 are associated with rxb1. 17.4.2 message acceptance filters the message acceptance filters and masks are used to determine if a message in the message assembly buffer should be loaded into either of the receive buff- ers. once a valid message has been received into the message assembly buffer (mab), the identifier fields of the message are compared to the filter values. if there is a match, that message will be loaded into the appropriate receive buffer. the acceptance filter looks at incoming messages for the rxide bit (cirxnsid<0>) to determine how to compare the identifiers. if the rxide bit is clear, the message is a standard frame and only filters with the exide bit (cirxfnsid<0>) clear are compared. if the rxide bit is set, the message is an extended frame, and only filters with the exide bit set are compared. configuring the rxm<1:0> bits to ? 01 ? or ? 10 ? can override the exide bit. 17.4.3 message acceptance filter masks the mask bits essentially determine which bits to apply the filter to. if any mask bit is set to a zero, then that bit will automatically be accepted regardless of the filter bit. there are 2 programmable acceptance filter masks associated with the receive buffers, one for each buffer. 17.4.4 receive overrun an overrun condition occurs when the message assembly buffer (mab) has assembled a valid received message, the message is accepted through the acceptance filters, and when the receive buffer associated with the filter has not been designated as clear of the previous message. the overrun error flag, rxnovr (ciintf<15> or ciintf<14>), and the errif bit (ciintf<5>) will be set and the message in the mab will be discarded. if the dben bit is clear, rxb1 and rxb0 operate inde- pendently. when this is the case, a message intended for rxb0 will not be diverted into rxb1 if rxb0 con- tains an unread message and the rx0ovr bit will be set. if the dben bit is set, the overrun for rxb0 is handled differently. if a valid message is received for rxb0 and rxful = 1 indicates that rxb0 is full and rxful = 0 indicates that rxb1 is empty, the message for rxb0 will be loaded into rxb1. an overrun error will not be generated for rxb0. if a valid message is received for rxb0 and rxful = 1 , indicating that both rxb0 and rxb1 are full, the message will be lost and an overrun will be indicated for rxb1. 17.4.5 receive errors the can module will detect the following receive errors: ? cyclic redundancy check (crc) error ? bit stuffing error ? invalid message receive error these receive errors do not generate an interrupt. however, the receive error counter is incremented by one in case one of these errors occur. the rxwar bit (ciintf<9>) indicates that the receive error counter has reached the cpu warning limit of 96 and an interrupt is generated. 17.4.6 receive interrupts receive interrupts can be divided into 3 major groups, each including various conditions that generate interrupts: ? receive interrupt: a message has been successfully received and loaded into one of the receive buffers. this inter- rupt is activated immediately after receiving the end of frame (eof) field. reading the rxnif flag will indicate which receive buffer caused the interrupt. ? wake-up interrupt: the can module has woken up from disable mode or the device has woken up from sleep mode.
? 2006 microchip technology inc. ds70117f-page 115 dspic30f6011/6012/6013/6014 ? receive error interrupts: a receive error interrupt will be indicated by the errif bit. this bit shows that an error condition occurred. the source of the error can be deter- mined by checking the bits in the can interrupt status register, ciintf. - invalid message received: if any type of error occurred during reception of the last message, an error will be indicated by the ivrif bit. - receiver overrun: the rxnovr bit indicates that an overrun condition occurred. - receiver warning: the rxwar bit indicates that the receive error counter (rerrcnt<7:0>) has reached the warning limit of 96. - receiver error passive: the rxep bit indicates that the receive error counter has exceeded the error passive limit of 127 and the module has gone into error passive state. 17.5 message transmission 17.5.1 transmit buffers the can module has three transmit buffers. each of the three buffers occupies 14 bytes of data. eight of the bytes are the maximum 8 bytes of the transmitted mes- sage. five bytes hold the standard and extended identifiers and other message arbitration information. 17.5.2 transmit message priority transmit priority is a prioritization within each node of the pending transmittable messages. there are 4 levels of transmit priority. if txpri<1:0> (citxncon<1:0>, where n = 0, 1 or 2 represents a par- ticular transmit buffer) for a particular message buffer is set to ? 11 ?, that buffer has the highest priority. if txpri<1:0> for a particular message buffer is set to ? 10 ? or ? 01 ?, that buffer has an intermediate priority. if txpri<1:0> for a particular message buffer is ? 00 ?, that buffer has the lowest priority. 17.5.3 transmission sequence to initiate transmission of the message, the txreq bit (citxncon<3>) must be set. the can bus module resolves any timing conflicts between setting of the txreq bit and the start of frame (sof), ensuring that if the priority was changed, it is resolved correctly before the sof occurs. when txreq is set, the txabt (citxncon<6>), txlarb (citxncon<5>) and txerr (citxncon<4>) flag bits are automatically cleared. setting txreq bit simply flags a message buffer as enqueued for transmission. when the module detects an available bus, it begins transmitting the message which has been determined to have the highest priority. if the transmission completes successfully on the first attempt, the txreq bit is cleared automatically, and an interrupt is generated if txie was set. if the message transmission fails, one of the error con- dition flags will be set, and the txreq bit will remain set indicating that the message is still pending for trans- mission. if the message encountered an error condition during the transmission attempt, the txerr bit will be set, and the error condition may cause an interrupt. if the message loses arbitration during the transmission attempt, the txlarb bit is set. no interrupt is generated to signal the loss of arbitration. 17.5.4 aborting message transmission the system can also abort a message by clearing the txreq bit associated with each message buffer. set- ting the abat bit (cictrl<12>) will request an abort of all pending messages. if the message has not yet started transmission, or if the message started but is interrupted by loss of arbitration or an error, the abort will be processed. the abort is indicated when the module sets the txabt bit and the txnif flag is not automatically set. 17.5.5 transmission errors the can module will detect the following transmission errors: ? acknowledge error ? form error ? bit error these transmission errors will not necessarily generate an interrupt but are indicated by the transmission error counter. however, each of these errors will cause the transmission error counter to be incremented by one. once the value of the error counter exceeds the value of 96, the errif (ciintf<5>) and the txwar bit (ciintf<10>) are set. once the value of the error counter exceeds the value of 96, an interrupt is generated and the txwar bit in the error flag register is set.
dspic30f6011/6012/6013/6014 ds70117f-page 116 ? 2006 microchip technology inc. 17.5.6 transmit interrupts transmit interrupts can be divided into 2 major groups, each including various conditions that generate interrupts: ? transmit interrupt: at least one of the three transmit buffers is empty (not scheduled) and can be loaded to schedule a message for transmission. reading the txnif flags will indicate which transmit buffer is available and caused the interrupt. ? transmit error interrupts: a transmission error interrupt will be indicated by the errif flag. this flag shows that an error con- dition occurred. the source of the error can be determined by checking the error flags in the can interrupt status register, ciintf. the flags in this register are related to receive and transmit errors. - transmitter warning interrupt: the txwar bit indicates that the transmit error counter has reached the cpu warning limit of 96. - transmitter error passive: the txep bit (ciintf<12>) indicates that the transmit error counter has exceeded the error passive limit of 127 and the module has gone to error passive state. - bus off: the txbo bit (ciintf<13>) indicates that the transmit error counter has exceeded 255 and the module has gone to the bus off state. 17.6 baud rate setting all nodes on any particular can bus must have the same nominal bit rate. in order to set the baud rate, the following parameters have to be initialized: ? synchronization jump width ? baud rate prescaler ? phase segments ? length determination of phase segment 2 ? sample point ? propagation segment bits 17.6.1 bit timing all controllers on the can bus must have the same baud rate and bit length. however, different controllers are not required to have the same master oscillator clock. at different clock frequencies of the individual controllers, the baud rate has to be adjusted by adjusting the number of time quanta in each segment. the nominal bit time can be thought of as being divided into separate non-overlapping time segments. these segments are shown in figure 17-2. ? synchronization segment (sync seg) ? propagation time segment (prop seg) ? phase segment 1 (phase1 seg) ? phase segment 2 (phase2 seg) the time segments and also the nominal bit time are made up of integer units of time called time quanta or t q . by definition, the nominal bit time has a minimum of 8 t q and a maximum of 25 t q . also, by definition, the minimum nominal bit time is 1 sec corresponding to a maximum bit rate of 1 mhz. figure 17-2: can bit timing input signal sync prop segment phase segment 1 phase segment 2 sync sample point t q
? 2006 microchip technology inc. ds70117f-page 117 dspic30f6011/6012/6013/6014 17.6.2 prescaler setting there is a programmable prescaler with integral values ranging from 1 to 64, in addition to a fixed divide-by-2 for clock generation. the time quantum (t q ) is a fixed unit of time derived from the oscillator period, and is given by equation 17-1. . equation 17-1: time quantum for clock generation 17.6.3 propagation segment this part of the bit time is used to compensate physical delay times within the network. these delay times con- sist of the signal propagation time on the bus line and the internal delay time of the nodes. the prop seg can be programmed from 1 t q to 8 t q by setting the prseg<2:0> bits (cicfg2<2:0>). 17.6.4 phase segments the phase segments are used to optimally locate the sampling of the received bit within the transmitted bit time. the sampling point is between phase1 seg and phase2 seg. these segments are lengthened or short- ened by resynchronization. the end of the phase1 seg determines the sampling point within a bit period. the segment is programmable from 1 t q to 8 t q . phase2 seg provides delay to the next transmitted data transi- tion. the segment is programmable from 1 t q to 8 t q , or it may be defined to be equal to the greater of phase1 seg or the information processing time (2 t q ). the phase1 seg is initialized by setting bits seg1ph<2:0> (cicfg2<5:3>), and phase2 seg is initialized by setting seg2ph<2:0> (cicfg2<10:8>). the following requirement must be fulfilled while setting the lengths of the phase segments: prop seg + phase1 seg > = phase2 seg 17.6.5 sample point the sample point is the point of time at which the bus level is read and interpreted as the value of that respec- tive bit. the location is at the end of phase1 seg. if the bit timing is slow and contains many t q , it is possible to specify multiple sampling of the bus line at the sample point. the level determined by the can bus then corre- sponds to the result from the majority decision of three values. the majority samples are taken at the sample point and twice before with a distance of t q /2. the can module allows the user to choose between sam- pling three times at the same point or once at the same point, by setting or clearing the sam bit (cicfg2<6>). typically, the sampling of the bit should take place at about 60-70% through the bit time, depending on the system parameters. 17.6.6 synchronization to compensate for phase shifts between the oscillator frequencies of the different bus stations, each can controller must be able to synchronize to the relevant signal edge of the incoming signal. when an edge in the transmitted data is detected, the logic will compare the location of the edge to the expected time (synchro- nous segment). the circuit will then adjust the values of phase1 seg and phase2 seg. there are 2 mechanisms used to synchronize. 17.6.6.1 hard synchronization hard synchronization is only done whenever there is a ?recessive? to ?dominant? edge during bus idle indicating the start of a message. after hard synchronization, the bit time counters are restarted with the sync seg. hard synchronization forces the edge which has caused the hard synchronization to lie within the synchronization segment of the restarted bit time. if a hard synchroniza- tion is done, there will not be a resynchronization within that bit time. 17.6.6.2 resynchronization as a result of resynchronization, phase1 seg may be lengthened or phase2 seg may be shortened. the amount of lengthening or shortening of the phase buffer segment has an upper bound known as the syn- chronization jump width, and is specified by the sjw<1:0> bits (cicfg1<7:6>). the value of the syn- chronization jump width will be added to phase1 seg or subtracted from phase2 seg. the resynchronization jump width is programmable between 1 t q and 4 t q . the following requirement must be fulfilled while setting the sjw<1:0> bits: phase2 seg > synchronization jump width note: f can must not exceed 30 mhz. if cancks = 0 , then f cy must not exceed 7.5 mhz. t q = 2 (brp<5:0> + 1)/f can
dspic30f6011/6012/6013/6014 ds70117f-page 118 ? 2006 microchip technology inc. table 17-1: can1 register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 b it 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state c1rxf0sid 0300 ? ? ? receive acceptance filter 0 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c1rxf0eidh 0302 ? ? ? ? receive acceptance filter 0 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxf0eidl 0304 receive acceptance filter 0 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1rxf1sid 0308 ? ? ? receive acceptance filter 1 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c1rxf1eidh 030a ? ? ? ? receive acceptance filter 1 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxf1eidl 030c receive acceptance filter 1 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1rxf2sid 0310 ? ? ? receive acceptance filter 2 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c1rxf2eidh 0312 ? ? ? ? receive acceptance filter 2 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxf2eidl 0314 receive acceptance filter 2 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1rxf3sid 0318 ? ? ? receive acceptance filter 3 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c1rxf3eidh 031a ? ? ? ? receive acceptance filter 3 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxf3eidl 031c receive acceptance filter 3 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1rxf4sid 0320 ? ? ? receive acceptance filter 4 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c1rxf4eidh 0322 ? ? ? ? receive acceptance filter 4 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxf4eidl 0324 receive acceptance filter 4 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1rxf5sid 0328 ? ? ? receive acceptance filter 5 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c1rxf5eidh 032a ? ? ? ? receive acceptance filter 5 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxf5eidl 032c receive acceptance filter 5 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1rxm0sid 0330 ? ? ? receive acceptance mask 0 standard identifier <10:0> ?mide 000u uuuu uuuu uu0u c1rxm0eidh 0332 ? ? ? ? receive acceptance mask 0 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxm0eidl 0334 receive acceptance mask 0 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1rxm1sid 0338 ? ? ? receive acceptance mask 1 standard identifier <10:0> ?mide 000u uuuu uuuu uu0u c1rxm1eidh 033a ? ? ? ? receive acceptance mask 1 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rxm1eidl 033c receive acceptance mask 1 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c1tx2sid 0340 transmit buffer 2 standard identifier <10:6> ? ? ? transmit buffer 2 standard identifier <5:0> srr txide uuuu u000 uuuu uuuu c1tx2eid 0342 transmit buffer 2 extended identifier <17:14> ? ? ? ? transmit buffer 2 extended identifier <13:6> uuuu 0000 uuuu uuuu c1tx2dlc 0344 transmit buffer 2 extended identifier <5:0> txrtr txrb1 txrb0 dlc<3:0> ? ? ? uuuu uuuu uuuu u000 c1tx2b1 0346 transmit buffer 2 byte 1 transmit buffer 2 byte 0 uuuu uuuu uuuu uuuu c1tx2b2 0348 transmit buffer 2 byte 3 transmit buffer 2 byte 2 uuuu uuuu uuuu uuuu c1tx2b3 034a transmit buffer 2 byte 5 transmit buffer 2 byte 4 uuuu uuuu uuuu uuuu c1tx2b4 034c transmit buffer 2 byte 7 transmit buffer 2 byte 6 uuuu uuuu uuuu uuuu c1tx2con 034e ? ? ? ? ? ? ? ? ? txabt txlarb txerr txreq ? txpri<1:0> 0000 0000 0000 0000 c1tx1sid 0350 transmit buffer 1 standard identifier <10:6> ? ? ? transmit buffer 1 standard identifier <5:0> srr txide uuuu u000 uuuu uuuu legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 119 dspic30f6011/6012/6013/6014 c1tx1eid 0352 transmit buffer 1 extended identifier <17:14> ? ? ? ? transmit buffer 1 extended identifier <13:6> uuuu 0000 uuuu uuuu c1tx1dlc 0354 transmit buffer 1 extended identifier <5:0> txrtr txrb1 txrb0 dlc<3:0> ? ? ? uuuu uuuu uuuu u000 c1tx1b1 0356 transmit buffer 1 byte 1 transmit buffer 1 byte 0 uuuu uuuu uuuu uuuu c1tx1b2 0358 transmit buffer 1 byte 3 transmit buffer 1 byte 2 uuuu uuuu uuuu uuuu c1tx1b3 035a transmit buffer 1 byte 5 transmit buffer 1 byte 4 uuuu uuuu uuuu uuuu c1tx1b4 035c transmit buffer 1 byte 7 transmit buffer 1 byte 6 uuuu uuuu uuuu uuuu c1tx1con 035e ? ? ? ? ? ? ? ? ? txabt txlarb txerr txreq ? txpri<1:0> 0000 0000 0000 0000 c1tx0sid 0360 transmit buffer 0 standard identifier <10:6> ? ? ? transmit buffer 0 standard identifier <5:0> srr txide uuuu u000 uuuu uuuu c1tx0eid 0362 transmit buffer 0 extended identifier <17:14> ? ? ? ? transmit buffer 0 extended identifier <13:6> uuuu 0000 uuuu uuuu c1tx0dlc 0364 transmit buffer 0 extended identifier <5:0> txrtr txrb1 txrb0 dlc<3:0> ? ? ? uuuu uuuu uuuu u000 c1tx0b1 0366 transmit buffer 0 byte 1 transmit buffer 0 byte 0 uuuu uuuu uuuu uuuu c1tx0b2 0368 transmit buffer 0 byte 3 transmit buffer 0 byte 2 uuuu uuuu uuuu uuuu c1tx0b3 036a transmit buffer 0 byte 5 transmit buffer 0 byte 4 uuuu uuuu uuuu uuuu c1tx0b4 036c transmit buffer 0 byte 7 transmit buffer 0 byte 6 uuuu uuuu uuuu uuuu c1tx0con 036e ? ? ? ? ? ? ? ? ? txabt txlarb txerr txreq ? txpri<1:0> 0000 0000 0000 0000 c1rx1sid 0370 ? ? ? receive buffer 1 standard identifier <10:0> srr rxide 000u uuuu uuuu uuuu c1rx1eid 0372 ? ? ? ? receive buffer 1 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rx1dlc 0374 receive buffer 1 extended identifier <5:0> rxrtr rxrb1 ? ? ? rxrb0 dlc<3:0> uuuu uuuu 000u uuuu c1rx1b1 0376 receive buffer 1 byte 1 receive buffer 1 byte 0 uuuu uuuu uuuu uuuu c1rx1b2 0378 receive buffer 1 byte 3 receive buffer 1 byte 2 uuuu uuuu uuuu uuuu c1rx1b3 037a receive buffer 1 byte 5 receive buffer 1 byte 4 uuuu uuuu uuuu uuuu c1rx1b4 037c receive buffer 1 byte 7 receive buffer 1 byte 6 uuuu uuuu uuuu uuuu c1rx1con 037e ? ? ? ? ? ? ? ?rxful ? ? ? rxrtrro filhit<2:0> 0000 0000 0000 0000 c1rx0sid 0380 ? ? ? receive buffer 0 standard identifier <10:0> srr rxide 000u uuuu uuuu uuuu c1rx0eid 0382 ? ? ? ? receive buffer 0 extended identifier <17:6> 0000 uuuu uuuu uuuu c1rx0dlc 0384 receive buffer 0 extended identifier <5:0> rxrtr rxrb1 ? ? ? rxrb0 dlc<3:0> uuuu uuuu 000u uuuu c1rx0b1 0386 receive buffer 0 byte 1 receive buffer 0 byte 0 uuuu uuuu uuuu uuuu c1rx0b2 0388 receive buffer 0 byte 3 receive buffer 0 byte 2 uuuu uuuu uuuu uuuu c1rx0b3 038a receive buffer 0 byte 5 receive buffer 0 byte 4 uuuu uuuu uuuu uuuu c1rx0b4 038c receive buffer 0 byte 7 receive buffer 0 byte 6 uuuu uuuu uuuu uuuu c1rx0con 038e ? ? ? ? ? ? ? ?rxful ? ? ? rxrtrro dben jtoff filhit0 0000 0000 0000 0000 c1ctrl 0390 cancap ? csidle abat cancks reqop<2:0> opmode<2:0> ? icode<2:0> ? 0000 0100 1000 0000 c1cfg1 0392 ? ? ? ? ? ? ? ? sjw<1:0> brp<5:0> 0000 0000 0000 0000 c1cfg2 0394 ?wakfil ? ? ? seg2ph<2:0> seg2phts sam seg1ph<2:0> prseg<2:0> 0u00 0uuu uuuu uuuu c1intf 0396 rx0ovr rx1ovr txbo txep rxep txwar rxwar ewarn ivrif wakif errif tx2if tx1if tx0if rx1if rx0if 0000 0000 0000 0000 table 17-1: can1 register map (continued) sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 b it 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 120 ? 2006 microchip technology inc. c1inte 0398 ? ? ? ? ? ? ? ? ivrie wakie errie tx2ie tx1ie tx0ie rx1e rx0ie 0000 0000 0000 0000 c1ec 039a transmit error count register receive error count register 0000 0000 0000 0000 table 17-1: can1 register map (continued) sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 b it 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 121 dspic30f6011/6012/6013/6014 table 17-2: can2 register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state c2rxf0sid 03c0 ? ? ? receive acceptance filter 0 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c2rxf0eidh 03c2 ? ? ? ? receive acceptance filter 0 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxf0eidl 03c4 receive acceptance filter 0 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2rxf1sid 03c8 ? ? ? receive acceptance filter 1 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c2rxf1eidh 03ca ? ? ? ? receive acceptance filter 1 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxf1eidl 03cc receive acceptance filter 1 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2rxf2sid 03d0 ? ? ? receive acceptance filter 2 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c2rxf2eidh 03d2 ? ? ? ? receive acceptance filter 2 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxf2eidl 03d4 receive acceptance filter 2 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2rxf3sid 03d8 ? ? ? receive acceptance filter 3 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c2rxf3eidh 03da ? ? ? ? receive acceptance filter 3 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxf3eidl 03dc receive acceptance filter 3 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2rxf4sid 03e0 ? ? ? receive acceptance filter 4 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c2rxf4eidh 03e2 ? ? ? ? receive acceptance filter 4 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxf4eidl 03e4 receive acceptance filter 4 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2rxf5sid 03e8 ? ? ? receive acceptance filter 5 standard identifier <10:0> ? exide 000u uuuu uuuu uu0u c2rxf5eidh 03ea ? ? ? ? receive acceptance filter 5 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxf5eidl 03ec receive acceptance filter 5 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2rxm0sid 03f0 ? ? ? receive acceptance mask 0 standard identifier <10:0> ?mide 000u uuuu uuuu uu0u c2rxm0eidh 03f2 ? ? ? ? receive acceptance mask 0 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxm0eidl 03f4 receive acceptance mask 0 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2rxm1sid 03f8 ? ? ? receive acceptance mask 1 standard identifier <10:0> ?mide 000u uuuu uuuu uu0u c2rxm1eidh 03fa ? ? ? ? receive acceptance mask 1 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rxm1eidl 03fc receive acceptance mask 1 extended identifier <5:0> ? ? ? ? ? ? ? ? ? ? uuuu uu00 0000 0000 c2tx2sid 0400 transmit buffer 2 standard identifier <10:6> ? ? ? transmit buffer 2 standard identifier <5:0> srr txide uuuu u000 uuuu uuuu c2tx2eid 0402 transmit buffer 2 extended identifier <17:14> ? ? ? ? transmit buffer 2 extended identifier <13:6> uuuu 0000 uuuu uuuu c2tx2dlc 0404 transmit buffer 2 extended identifier <5:0> txrtr txrb1 txrb0 dlc<3:0> ? ? ? uuuu uuuu uuuu u000 c2tx2b1 0406 transmit buffer 2 byte 1 transmit buffer 2 byte 0 uuuu uuuu uuuu uuuu c2tx2b2 0408 transmit buffer 2 byte 3 transmit buffer 2 byte 2 uuuu uuuu uuuu uuuu c2tx2b3 040a transmit buffer 2 byte 5 transmit buffer 2 byte 4 uuuu uuuu uuuu uuuu c2tx2b4 040c transmit buffer 2 byte 7 transmit buffer 2 byte 6 uuuu uuuu uuuu uuuu c2tx2con 040e ? ? ? ? ? ? ? ? ? txabt txlarb txerr txreq ? txpri<1:0> 0000 0000 0000 0000 c2tx1sid 0410 transmit buffer 1 standard identifier <10:6> ? ? ? transmit buffer 1 standard identifier <5:0> srr txide uuuu u000 uuuu uuuu legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 122 ? 2006 microchip technology inc. c2tx1eid 0412 transmit buffer 1 extended identifier <17:14> ? ? ? ? transmit buffer 1 extended identifier <13:6> uuuu 0000 uuuu uuuu c2tx1dlc 0414 transmit buffer 1 extended identifier <5:0> txrtr txrb1 txrb0 dlc<3:0> ? ? ? uuuu uuuu uuuu u000 c2tx1b1 0416 transmit buffer 1 byte 1 transmit buffer 1 byte 0 uuuu uuuu uuuu uuuu c2tx1b2 0418 transmit buffer 1 byte 3 transmit buffer 1 byte 2 uuuu uuuu uuuu uuuu c2tx1b3 041a transmit buffer 1 byte 5 transmit buffer 1 byte 4 uuuu uuuu uuuu uuuu c2tx1b4 041c transmit buffer 1 byte 7 transmit buffer 1 byte 6 uuuu uuuu uuuu uuuu c2tx1con 041e ? ? ? ? ? ? ? ? ? txabt txlarb txerr txreq ? txpri<1:0> 0000 0000 0000 0000 c2tx0sid 0420 transmit buffer 0 standard identifier <10:6> ? ? ? transmit buffer 0 standard identifier <5:0> srr txide uuuu u000 uuuu uuuu c2tx0eid 0422 transmit buffer 0 extended identifier <17:14> ? ? ? ? transmit buffer 0 extended identifier <13:6> uuuu 0000 uuuu uuuu c2tx0dlc 0424 transmit buffer 0 extended identifier <5:0> txrtr txrb1 txrb0 dlc<3:0> ? ? ? uuuu uuuu uuuu u000 c2tx0b1 0426 transmit buffer 0 byte 1 transmit buffer 0 byte 0 uuuu uuuu uuuu uuuu c2tx0b2 0428 transmit buffer 0 byte 3 transmit buffer 0 byte 2 uuuu uuuu uuuu uuuu c2tx0b3 042a transmit buffer 0 byte 5 transmit buffer 0 byte 4 uuuu uuuu uuuu uuuu c2tx0b4 042c transmit buffer 0 byte 7 transmit buffer 0 byte 6 uuuu uuuu uuuu uuuu c2tx0con 042e ? ? ? ? ? ? ? ? ? txabt txlarb txerr txreq ? txpri<1:0> 0000 0000 0000 0000 c2rx1sid 0430 ? ? ? receive buffer 1 standard identifier <10:0> srr rxide 000u uuuu uuuu uuuu c2rx1eid 0432 ? ? ? ? receive buffer 1 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rx1dlc 0434 receive buffer 1 extended identifier <5:0> rxrtr rxrb1 ? ? ? rxrb0 dlc<3:0> uuuu uuuu 000u uuuu c2rx1b1 0436 receive buffer 1 byte 1 receive buffer 1 byte 0 uuuu uuuu uuuu uuuu c2rx1b2 0438 receive buffer 1 byte 3 receive buffer 1 byte 2 uuuu uuuu uuuu uuuu c2rx1b3 043a receive buffer 1 byte 5 receive buffer 1 byte 4 uuuu uuuu uuuu uuuu c2rx1b4 043c receive buffer 1 byte 7 receive buffer 1 byte 6 uuuu uuuu uuuu uuuu c2rx1con 043e ? ? ? ? ? ? ? ?rxful ? ? ? rxrtrro filhit<2:0> 0000 0000 0000 0000 c2rx0sid 0440 ? ? ? receive buffer 0 standard identifier <10:0> srr rxide 000u uuuu uuuu uuuu c2rx0eid 0442 ? ? ? ? receive buffer 0 extended identifier <17:6> 0000 uuuu uuuu uuuu c2rx0dlc 0444 receive buffer 0 extended identifier <5:0> rxrtr rxrb1 ? ? ? rxrb0 dlc<3:0> uuuu uuuu 000u uuuu c2rx0b1 0446 receive buffer 0 byte 1 receive buffer 0 byte 0 uuuu uuuu uuuu uuuu c2rx0b2 0448 receive buffer 0 byte 3 receive buffer 0 byte 2 uuuu uuuu uuuu uuuu c2rx0b3 044a receive buffer 0 byte 5 receive buffer 0 byte 4 uuuu uuuu uuuu uuuu c2rx0b4 044c receive buffer 0 byte 7 receive buffer 0 byte 6 uuuu uuuu uuuu uuuu c2rx0con 044e ? ? ? ? ? ? ? ?rxful ? ? ? rxrtrro dben jtoff filhit0 0000 0000 0000 0000 c2ctrl 0450 cancap ? csidle abat cancks reqop<2:0> opmode<2:0> ? icode<2:0> ? 0000 0100 1000 0000 c2cfg1 0452 ? ? ? ? ? ? ? ? sjw<1:0> brp<5:0> 0000 0000 0000 0000 c2cfg2 0454 ? wakfil ? ? ? seg2ph<2:0> seg2phts sam seg1ph<2:0> prseg<2:0> 0u00 0uuu uuuu uuuu table 17-2: can2 register map (continued) sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 123 dspic30f6011/6012/6013/6014 c2intf 0456 rx0ovr rx1ovr txbo txep rxep txwar rxwar ewarn ivrif wakif errif tx2if tx1if tx0if rx1if rx0if 0000 0000 0000 0000 c2inte 0458 ? ? ? ? ? ? ? ? ivrie wakie errie tx2ie tx1ie tx0ie rx1e rx0ie 0000 0000 0000 0000 c2ec 045a transmit error count register receive error count register 0000 0000 0000 0000 table 17-2: can2 register map (continued) sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state legend: u = uninitialized bit note: refer to ? dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 124 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 125 dspic30f6011/6012/6013/6014 18.0 data converter interface (dci) module 18.1 module introduction the dspic30f data converter interface (dci) module allows simple interfacing of devices, such as audio coder/decoders (codecs), a/d converters and d/a converters. the following interfaces are supported: ? framed synchronous serial transfer (single or multi-channel) ? inter-ic sound (i 2 s) interface ? ac-link compliant mode the dci module provides the following general features: ? programmable word size up to 16 bits ? support for up to 16 time slots, for a maximum frame size of 256 bits ? data buffering for up to 4 samples without cpu overhead 18.2 module i/o pins there are four i/o pins associated with the module. when enabled, the module controls the data direction of each of the four pins. 18.2.1 csck pin the csck pin provides the serial clock for the dci module. the csck pin may be configured as an input or output using the csckd control bit in the dcicon1 sfr. when configured as an output, the serial clock is provided by the dspic30f. when configured as an input, the serial clock must be provided by an external device. 18.2.2 csdo pin the serial data output (csdo) pin is configured as an output only pin when the module is enabled. the csdo pin drives the serial bus whenever data is to be transmitted. the csdo pin is tri-stated or driven to ? 0 ? during csck periods when data is not transmitted, depending on the state of the csdom control bit. this allows other devices to place data on the serial bus during transmission periods not used by the dci module. 18.2.3 csdi pin the serial data input (csdi) pin is configured as an input only pin when the module is enabled. 18.2.3.1 cofs pin the codec frame synchronization (cofs) pin is used to synchronize data transfers that occur on the csdo and csdi pins. the cofs pin may be configured as an input or an output. the data direction for the cofs pin is determined by the cofsd control bit in the dcicon1 register. the dci module accesses the shadow registers while the cpu is in the process of accessing the memory mapped buffer registers. 18.2.4 buffer data alignment data values are always stored left justified in the buff- ers since most codec data is represented as a signed 2?s complement fractional number. if the received word length is less than 16 bits, the unused lsbs in the receive buffer registers are set to ? 0 ? by the module. if the transmitted word length is less than 16 bits, the unused lsbs in the transmit buffer register are ignored by the module. the word length setup is described in subsequent sections of this document. 18.2.5 transmit/receive shift register the dci module has a 16-bit shift register for shifting serial data in and out of the module. data is shifted in/ out of the shift register msb first, since audio pcm data is transmitted in signed 2?s complement format. 18.2.6 dci buffer control the dci module contains a buffer control unit for trans- ferring data between the shadow buffer memory and the serial shift register. the buffer control unit is a sim- ple 2-bit address counter that points to word locations in the shadow buffer memory. for the receive memory space (high address portion of dci buffer memory), the address counter is concatenated with a ? 0 ? in the msb location to form a 3-bit address. for the transmit mem- ory space (high portion of dci buffer memory), the address counter is concatenated with a ? 1 ? in the msb location. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). note: the dci buffer control unit always accesses the same relative location in the transmit and receive buffers, so only one address counter is provided.
dspic30f6011/6012/6013/6014 ds70117f-page 126 ? 2006 microchip technology inc. figure 18-1: dci module block diagram bcg control bits 16-bit data bus sample rate generator sckd fsd dci buffer frame synchronization generator control unit dci shift register receive buffer registers w/shadow f osc /4 word size selection bits frame length selection bits dci mode selection bits csck cofs csdi csdo 15 0 transmit buffer registers w/shadow
? 2006 microchip technology inc. ds70117f-page 127 dspic30f6011/6012/6013/6014 18.3 dci module operation 18.3.1 module enable the dci module is enabled or disabled by setting/ clearing the dcien control bit in the dcicon1 sfr. clearing the dcien control bit has the effect of reset- ting the module. in particular, all counters associated with csck generation, frame sync, and the dci buffer control unit are reset. the dci clocks are shutdown when the dcien bit is cleared. when enabled, the dci controls the data direction for the four i/o pins associated with the module. the port, lat and tris register values for these i/o pins are overridden by the dci module when the dcien bit is set. it is also possible to override the csck pin separately when the bit clock generator is enabled. this permits the bit clock generator to operate without enabling the rest of the dci module. 18.3.2 word size selection bits the ws<3:0> word size selection bits in the dcicon2 sfr determine the number of bits in each dci data word. essentially, the ws<3:0> bits determine the counting period for a 4-bit counter clocked from the csck signal. any data length, up to 16 bits, may be selected. the value loaded into the ws<3:0> bits is one less the desired word length. for example, a 16-bit data word size is selected when ws<3:0> = 1111 . 18.3.3 frame sync generator the frame sync generator (cofsg) is a 4-bit counter that sets the frame length in data words. the frame sync generator is incremented each time the word size counter is reset (refer to section 18.3.2 ?word size selection bits? ). the period for the frame synchroni- zation generator is set by writing the cofsg<3:0> control bits in the dcicon2 sfr. the cofsg period in clock cycles is determined by the following formula: equation 18-1: cofsg period frame lengths, up to 16 data words, may be selected. the frame length in csck periods can vary up to a maximum of 256 depending on the word size that is selected. 18.3.4 frame sync mode control bits the type of frame sync signal is selected using the frame synchronization mode control bits (cofsm<1:0>) in the dcicon1 sfr. the following operating modes can be selected: ? multi-channel mode ?i 2 s mode ? ac-link mode (16-bit) ? ac-link mode (20-bit) the operation of the cofsm control bits depends on whether the dci module generates the frame sync signal as a master device, or receives the frame sync signal as a slave device. the master device in a dsp/codec pair is the device that generates the frame sync signal. the frame sync signal initiates data transfers on the csdi and csdo pins and usually has the same frequency as the data sample rate (cofs). the dci module is a frame sync master if the cofsd control bit is cleared and is a frame sync slave if the cofsd control bit is set. 18.3.5 master frame sync operation when the dci module is operating as a frame sync master device (cofsd = 0 ), the cofsm mode bits determine the type of frame sync pulse that is generated by the frame sync generator logic. a new cofs signal is generated when the frame sync generator resets to ? 0 ?. in the multi-channel mode, the frame sync pulse is driven high for the csck period to initiate a data trans- fer. the number of csck cycles between successive frame sync pulses will depend on the word size and frame sync generator control bits. a timing diagram for the frame sync signal in multi-channel mode is shown in figure 18-2. in the ac-link mode of operation, the frame sync sig- nal has a fixed period and duty cycle. the ac-link frame sync signal is high for 16 csck cycles and is low for 240 csck cycles. a timing diagram with the timing details at the start of an ac-link frame is shown in figure 18-3. in the i 2 s mode, a frame sync signal having a 50% duty cycle is generated. the period of the i 2 s frame sync signal in csck cycles is determined by the word size and frame sync generator control bits. a new i 2 s data transfer boundary is marked by a high-to-low or a low-to-high transition edge on the cofs pin. note: these ws<3:0> control bits are used only in the multi-channel and i 2 s modes. these bits have no effect in ac-link mode since the data slot sizes are fixed by the protocol. note: the cofsg control bits will have no effect in ac-link mode since the frame length is set to 256 csck periods by the protocol. frame length = word length ? (fsg value + 1)
dspic30f6011/6012/6013/6014 ds70117f-page 128 ? 2006 microchip technology inc. 18.3.6 slave frame sync operation when the dci module is operating as a frame sync slave (cofsd = 1 ), data transfers are controlled by the codec device attached to the dci module. the cofsm control bits control how the dci module responds to incoming cofs signals. in the multi-channel mode, a new data frame transfer will begin one csck cycle after the cofs pin is sam- pled high (see figure 18-2). the pulse on the cofs pin resets the frame sync generator logic. in the i 2 s mode, a new data word will be transferred one csck cycle after a low-to-high or a high-to-low transition is sampled on the cofs pin. a rising or fall- ing edge on the cofs pin resets the frame sync generator logic. in the ac-link mode, the tag slot and subsequent data slots for the next frame will be transferred one csck cycle after the cofs pin is sampled high. the cofsg and ws bits must be configured to pro- vide the proper frame length when the module is oper- ating in the slave mode. once a valid frame sync pulse has been sampled by the module on the cofs pin, an entire data frame transfer will take place. the module will not respond to further frame sync pulses until the data frame transfer has completed. figure 18-2: frame sync timing, multi-channel mode figure 18-3: frame sync timi ng, ac-link start of frame figure 18-4: i 2 s interface frame sync timing csck csdi/csdo cofs msb lsb ta g msb bit_clk csdo or csdi sync ta g bit 14 s12 lsb s12 bit 1 s12 bit 2 ta g bit 13 msb lsb msb lsb csck csdi or csdo ws note: a 5-bit transfer is shown here for illustration purposes. the i 2 s protocol does not specify word length ? this will be system dependent.
? 2006 microchip technology inc. ds70117f-page 129 dspic30f6011/6012/6013/6014 18.3.7 bit clock generator the dci module has a dedicated 12-bit time base that produces the bit clock. the bit clock rate (period) is set by writing a non-zero 12-bit value to the bcg<11:0> control bits in the dcicon3 sfr. when the bcg<11:0> bits are set to zero, the bit clock will be disabled. if the bcg<11:0> bits are set to a non- zero value, the bit clock generator is enabled. these bits should be set to ? 0 ? and the csckd bit set to ? 1 ? if the serial clock for the dci is received from an external device. the formula for the bit clock frequency is given in equation 18-2. equation 18-2: bit clock frequency the required bit clock frequency will be determined by the system sampling rate and frame size. typical bit clock frequencies range from 16x to 512x, the con- verter sample rate depending on the data converter and the communication protocol that is used. to achieve bit clock frequencies associated with com- mon audio sampling rates, the user will need to select a crystal frequency that has an ?even? binary value. examples of such crystal frequencies are listed in table 18-1. table 18-1: device frequencies for common codec csck frequencies f bck = f cy 2 (bcg + 1) ? f s (khz) f csck /f s f csck (mhz) (1) f osc (mh z )pllf cy (mips) bcg (2) 8 256 2.048 8.192 4 8.192 1 12 256 3.072 6.144 8 12.288 1 32 32 1.024 8.192 8 16.384 7 44.1 32 1.4112 5.6448 8 11.2896 3 48 64 3.072 6.144 16 24.576 3 note 1: when the csck signal is applied externally (csckd = 1 ), the external clock high and low times must meet the device timing requirements. 2: when the csck signal is applied externally (csckd = 1 ), the bcg<11:0> bits have no effect on the operation of the dci module.
dspic30f6011/6012/6013/6014 ds70117f-page 130 ? 2006 microchip technology inc. 18.3.8 sample clock edge control bit the sample clock edge (cscke) control bit determines the sampling edge for the csck signal. if the csck bit is cleared (default), data will be sampled on the falling edge of the csck signal. the ac-link protocols and most multi-channel formats require that data be sam- pled on the falling edge of the csck signal. if the csck bit is set, data will be sampled on the rising edge of csck. the i 2 s protocol requires that data be sampled on the rising edge of the csck signal. 18.3.9 data justification control bit in most applications, the data transfer begins one csck cycle after the cofs signal is sampled active. this is the default configuration of the dci module. an alternate data alignment can be selected by setting the djst control bit in the dcicon1 sfr. when djst = 1 , data transfers will begin during the same csck cycle when the cofs signal is sampled active. 18.3.10 transmit slot enable bits the tscon sfr has control bits that are used to enable up to 16 time slots for transmission. these con- trol bits are the tse<15:0> bits. the size of each time slot is determined by the ws<3:0> word size selection bits and can vary up to 16 bits. if a transmit time slot is enabled via one of the tse bits (tsex = 1 ), the contents of the current transmit shadow buffer location will be loaded into the csdo shift regis- ter and the dci buffer control unit is incremented to point to the next location. during an unused transmit time slot, the csdo pin will drive ? 0 ?s or will be tri-stated during all disabled time slots depending on the state of the csdom bit in the dcicon1 sfr. the data frame size in bits is determined by the chosen data word size and the number of data word elements in the frame. if the chosen frame size has less than 16 elements, the additional slot enable bits will have no effect. each transmit data word is written to the 16-bit transmit buffer as left justified data. if the selected word size is less than 16 bits, then the lsbs of the transmit buffer memory will have no effect on the transmitted data. the user should write ? 0 ?s to the unused lsbs of each transmit buffer location. 18.3.11 receive slot enable bits the rscon sfr contains control bits that are used to enable up to 16 time slots for reception. these control bits are the rse<15:0> bits. the size of each receive time slot is determined by the ws<3:0> word size selection bits and can vary from 1 to 16 bits. if a receive time slot is enabled via one of the rse bits (rsex = 1 ), the shift register contents will be written to the current dci receive shadow buffer location and the buffer control unit will be incremented to point to the next buffer location. data is not packed in the receive memory buffer loca- tions if the selected word size is less than 16 bits. each received slot data word is stored in a separate 16-bit buffer location. data is always stored in a left justified format in the receive memory buffer. 18.3.12 slot enable bits operation with frame sync the tse and rse control bits operate in concert with the dci frame sync generator. in the master mode, a cofs signal is generated whenever the frame sync generator is reset. in the slave mode, the frame sync generator is reset whenever a cofs pulse is received. the tse and rse control bits allow up to 16 consecu- tive time slots to be enabled for transmit or receive. after the last enabled time slot has been transmitted/ received, the dci will stop buffering data until the next occurring cofs pulse. 18.3.13 synchronous data transfers the dci buffer control unit will be incremented by one word location whenever a given time slot has been enabled for transmission or reception. in most cases, data input and output transfers will be synchronized, which means that a data sample is received for a given channel at the same time a data sample is transmitted. therefore, the transmit and receive buffers will be filled with equal amounts of data when a dci interrupt is generated. in some cases, the amount of data transmitted and received during a data frame may not be equal. as an example, assume a two-word data frame is used. fur- thermore, assume that data is only received during slot #0 but is transmitted during slot #0 and slot #1. in this case, the buffer control unit counter would be incre- mented twice during a data frame but only one receive register location would be filled with data.
? 2006 microchip technology inc. ds70117f-page 131 dspic30f6011/6012/6013/6014 18.3.14 buffer length control the amount of data that is buffered between interrupts is determined by the buffer length (blen<1:0>) control bits in the dcicon2 sfr. the size of the transmit and receive buffers may be varied from 1 to 4 data words using the blen control bits. the blen control bits are compared to the current value of the dci buffer control unit address counter. when the 2 lsbs of the dci address counter match the blen<1:0> value, the buffer control unit will be reset to ? 0 ?. in addition, the contents of the receive shadow registers are trans- ferred to the receive buffer registers and the contents of the transmit buffer registers are transferred to the transmit shadow registers. 18.3.15 buffer alignment with data frames there is no direct coupling between the position of the agu address pointer and the data frame boundaries. this means that there will be an implied assignment of each transmit and receive buffer that is a function of the blen control bits and the number of enabled data slots via the tse and rse control bits. as an example, assume that a 4-word data frame is chosen and that we want to transmit on all four time slots in the frame. this configuration would be estab- lished by setting the tse0, tse1, tse2, and tse3 control bits in the tscon sfr. with this module setup, the txbuf0 register would be naturally assigned to slot #0, the txbuf1 register would be naturally assigned to slot #1, and so on. 18.3.16 transmit status bits there are two transmit status bits in the dcistat sfr. the tmpty bit is set when the contents of the transmit buffer registers are transferred to the transmit shadow registers. the tmpty bit may be polled in software to determine when the transmit buffer registers may be written. the tmpty bit is cleared automatically by the hardware when a write to one of the four transmit buffers occurs. the tunf bit is read only and indicates that a transmit underflow has occurred for at least one of the transmit buffer registers that is in use. the tunf bit is set at the time the transmit buffer registers are transferred to the transmit shadow registers. the tunf status bit is cleared automatically when the buffer register that underflowed is written by the cpu. 18.3.17 receive status bits there are two receive status bits in the dcistat sfr. the rful status bit is read only and indicates that new data is available in the receive buffers. the rful bit is cleared automatically when all receive buffers in use have been read by the cpu. the rov status bit is read only and indicates that a receive overflow has occurred for at least one of the receive buffer locations. a receive overflow occurs when the buffer location is not read by the cpu before new data is transferred from the shadow registers. the rov status bit is cleared automatically when the buffer register that caused the overflow is read by the cpu. when a receive overflow occurs for a specific buffer location, the old contents of the buffer are overwritten. note: when more than four time slots are active within a data frame, the user code must keep track of which time slots are to be read/written at each interrupt. in some cases, the alignment between transmit/ receive buffers and their respective slot assignments could be lost. examples of such cases include an emulation break- point or a hardware trap. in these situa- tions, the user should poll the slot status bits to determine what data should be loaded into the buffer registers to resynchronize the software with the dci module. note: the transmit status bits only indicate sta- tus for buffer locations that are used by the module. if the buffer length is set to less than four words, for example, the unused buffer locations will not affect the transmit status bits. note: the receive status bits only indicate status for buffer locations that are used by the module. if the buffer length is set to less than four words, for example, the unused buffer locations will not affect the transmit status bits.
dspic30f6011/6012/6013/6014 ds70117f-page 132 ? 2006 microchip technology inc. 18.3.18 slot status bits the slot<3:0> status bits in the dcistat sfr indi- cate the current active time slot. these bits will corre- spond to the value of the frame sync generator counter. the user may poll these status bits in software when a dci interrupt occurs to determine what time slot data was last received and which time slot data should be loaded into the txbuf registers. 18.3.19 csdo mode bit the csdom control bit controls the behavior of the csdo pin during unused transmit slots. a given trans- mit time slot is unused if it?s corresponding tsex bit in the tscon sfr is cleared. if the csdom bit is cleared (default), the csdo pin will be low during unused time slot periods. this mode will be used when there are only two devices attached to the serial bus. if the csdom bit is set, the csdo pin will be tri-stated during unused time slot periods. this mode allows mul- tiple devices to share the same csdo line in a multi- channel application. each device on the csdo line is configured so that it will only transmit data during specific time slots. no two devices will transmit data during the same time slot. 18.3.20 digital loopback mode digital loopback mode is enabled by setting the dloop control bit in the dcistat sfr. when the dloop bit is set, the module internally connects the csdo signal to csdi. the actual data input on the csdi i/o pin will be ignored in digital loopback mode. 18.3.21 underflow mo de control bit when an underflow occurs, one of two actions may occur depending on the state of the underflow mode (unfm) control bit in the dcicon1 sfr. if the unfm bit is cleared (default), the module will transmit ? 0 ?s on the csdo pin during the active time slot for the buffer location. in this operating mode, the codec device attached to the dci module will simply be fed digital ?silence?. if the unfm control bit is set, the module will transmit the last data written to the buffer location. this operating mode permits the user to send continuous data to the codec device without consuming cpu overhead. 18.4 dci module interrupts the frequency of dci module interrupts is dependent on the blen<1:0> control bits in the dcicon2 sfr. an interrupt to the cpu is generated each time the set buffer length has been reached and a shadow register transfer takes place. a shadow register transfer is defined as the time when the previously written txbuf values are transferred to the transmit shadow registers and new received values in the receive shadow registers are transferred into the rxbuf registers. 18.5 dci module operation during cpu sleep and idle modes 18.5.1 dci module operation during cpu sleep mode the dci module has the ability to operate while in sleep mode and wake the cpu when the csck signal is supplied by an external device (csckd = 1 ). the dci module will generate an asynchronous interrupt when a dci buffer transfer has completed and the cpu is in sleep mode. 18.5.2 dci module operation during cpu idle mode if the dcisidl control bit is cleared (default), the mod- ule will continue to operate normally even in idle mode. if the dcisidl bit is set, the module will halt when idle mode is asserted. 18.6 ac-link mode operation the ac-link protocol is a 256-bit frame with one 16-bit data slot, followed by twelve 20-bit data slots. the dci module has two operating modes for the ac-link pro- tocol. these operating modes are selected by the cofsm<1:0> control bits in the dcicon1 sfr. the first ac-link mode is called ?16-bit ac-link mode? and is selected by setting cofsm<1:0> = 10 . the second ac-link mode is called ?20-bit ac-link mode? and is selected by setting cofsm<1:0> = 11 . 18.6.1 16-bit ac-link mode in the 16-bit ac-link mode, data word lengths are restricted to 16 bits. note that this restriction only affects the 20-bit data time slots of the ac-link proto- col. for received time slots, the incoming data is simply truncated to 16 bits. for outgoing time slots, the 4 lsbs of the data word are set to ? 0 ? by the module. this trun- cation of the time slots limits the a/d and dac data to 16 bits but permits proper data alignment in the txbuf and rxbuf registers. each rxbuf and txbuf regis- ter will contain one data time slot value. 18.6.2 20-bit ac-link mode the 20-bit ac-link mode allows all bits in the data time slots to be transmitted and received but does not main- tain data alignment in the txbuf and rxbuf registers. the 20-bit ac-link mode functions similar to the multi- channel mode of the dci module, except for the duty cycle of the frame synchronization signal. the ac-link frame synchronization signal should remain high for 16 csck cycles and should be low for the following 240 cycles.
? 2006 microchip technology inc. ds70117f-page 133 dspic30f6011/6012/6013/6014 the 20-bit mode treats each 256-bit ac-link frame as sixteen, 16-bit time slots. in the 20-bit ac-link mode, the module operates as if cofsg<3:0> = 1111 and ws<3:0> = 1111 . the data alignment for 20-bit data slots is ignored. for example, an entire ac-link data frame can be transmitted and received in a packed fashion by setting all bits in the tscon and rscon sfrs. since the total available buffer length is 64 bits, it would take 4 consecutive interrupts to transfer the ac-link frame. the application software must keep track of the current ac-link frame segment. 18.7 i 2 s mode operation the dci module is configured for i 2 s mode by writing a value of ? 01 ? to the cofsm<1:0> control bits in the dcicon1 sfr. when operating in the i 2 s mode, the dci module will generate frame synchronization sig- nals with a 50% duty cycle. each edge of the frame synchronization signal marks the boundary of a new data word transfer. the user must also select the frame length and data word size using the cofsg and ws control bits in the dcicon2 sfr. 18.7.1 i 2 s frame and data word length selection the ws and cofsg control bits are set to produce the period for one half of an i 2 s data frame. that is, the frame length is the total number of csck cycles required for a left or a right data word transfer. the blen bits must be set for the desired buffer length. setting blen<1:0> = 01 will produce a cpu interrupt, once per i 2 s frame. 18.7.2 i 2 s data justification as per the i 2 s specification, a data word transfer will, by default, begin one csck cycle after a transition of the ws signal. a ?ms bit left justified? option can be selected using the djst control bit in the dcicon2 sfr. if djst = 1 , the i 2 s data transfers will be msb left jus- tified. the msb of the data word will be presented on the csdo pin during the same csck cycle as the ris- ing or falling edge of the cofs signal. the csdo pin is tri-stated after the data word has been sent.
dspic30f6011/6012/6013/6014 ds70117f-page 134 ? 2006 microchip technology inc. table 18-2: dci register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state dcicon1 0240 dcien ? dcisidl ? dloop csckd cscke cofsd unfm csdom djst ? ? ? cofsm1 cofsm0 0000 0000 0000 0000 dcicon2 0242 ? ? ? ? blen1 blen0 ? cofsg<3:0> ? ws<3:0> 0000 0000 0000 0000 dcicon3 0244 ? ? ? ? bcg<11:0> 0000 0000 0000 0000 dcistat 0246 ? ? ? ? slot3 slot2 slot1 slot0 ? ? ? ? rov rful tunf tmpty 0000 0000 0000 0000 tscon 0248 tse15 tse14 tse13 tse12 tse11 tse10 tse9 tse8 tse7 tse6 tse5 tse4 tse3 tse2 tse1 tse0 0000 0000 0000 0000 rscon 024c rse15 rse14 rse13 rse12 rse11 rse10 rse9 rse8 rse7 rse6 rse5 r se4 rse3 rse2 rse1 rse0 0000 0000 0000 0000 rxbuf0 0250 receive buffer #0 data register 0000 0000 0000 0000 rxbuf1 0252 receive buffer #1 data register 0000 0000 0000 0000 rxbuf2 0254 receive buffer #2 data register 0000 0000 0000 0000 rxbuf3 0256 receive buffer #3 data register 0000 0000 0000 0000 txbuf0 0258 transmit buffer #0 data register 0000 0000 0000 0000 txbuf1 025a transmit buffer #1 data register 0000 0000 0000 0000 txbuf2 025c transmit buffer #2 data register 0000 0000 0000 0000 txbuf3 025e transmit buffer #3 data register 0000 0000 0000 0000 note: refer to ?dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 135 dspic30f6011/6012/6013/6014 19.0 12-bit analog-to-digital converter (a/d) module the 12-bit analog-to-digital converter (adc) allows conversion of an analog input signal to a 12-bit digital number. this module is based on a successive approximation register (sar) architecture and pro- vides a maximum sampling rate of 200 ksps. the adc module has up to 16 analog inputs which are multi- plexed into a sample and hold amplifier. the output of the sample and hold is the input into the converter which generates the result. the analog reference volt- age is software selectable to either the device supply voltage (av dd /av ss ) or the voltage level on the (v ref +/v ref -) pin. the adc has a unique feature of being able to operate while the device is in sleep mode with rc oscillator selection. the adc module has six 16-bit registers: ? adc control register 1 (adcon1) ? adc control register 2 (adcon2) ? adc control register 3 (adcon3) ? adc input select register (adchs) ? adc port configuration register (adpcfg) ? adc input scan selection register (adcssl) the adcon1, adcon2 and adcon3 registers con- trol the operation of the a/d module. the adchs reg- ister selects the input channels to be converted. the adpcfg register configures the port pins as analog inputs or as digital i/o. the adcssl register selects inputs for scanning. the block diagram of the 12-bit adc module is shown in figure 19-1. figure 19-1: 12-bit adc f unctional block diagram note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). note: the ssrc<2:0>, asam, smpi<3:0>, bufm and alts bits, as well as the adcon3 and adcssl registers, must not be written to while adon = 1 . this would lead to indeterminate results. comparator 12-bit sar conversion logic v ref + dac data 16-word, 12-bit dual port ram bus interface an12 0000 0101 0111 1001 1101 1110 1111 1100 0001 0010 0011 0100 0110 1000 1010 1011 an13 an14 an15 an8 an9 an10 an11 an4 an5 an6 an7 an0 an1 an2 an3 ch0 an1 v ref - v ref - sample/sequence control sample input mux control input switches s/h av ss av dd format
dspic30f6011/6012/6013/6014 ds70117f-page 136 ? 2006 microchip technology inc. 19.1 adc result buffer the module contains a 16-word dual port read only buffer, called adcbuf0...adcbuff, to buffer the adc results. the ram is 12 bits wide but the data obtained is represented in one of four different 16-bit data for- mats. the contents of the sixteen a/d conversion result buffer registers, adcbuf0 through adcbuff, cannot be written by user software. 19.2 conversion operation after the adc module has been configured, the sample acquisition is started by setting the samp bit. various sources, such as a programmable bit, timer time-outs and external events, will terminate acquisition and start a conversion. when the a/d conversion is complete, the result is loaded into adcbuf0...adcbuff, and the done bit and the a/d interrupt flag adif are set after the number of samples specified by the smpi bit. the adc module can be configured for different interrupt rates as described in section 19.3 ?selecting the conversion sequence? . the following steps should be followed for doing an a/d conversion: 1. configure the adc module: ? configure analog pins, voltage reference and digital i/o ? select adc input channels ? select adc conversion clock ? select adc conversion trigger ? turn on adc module 2. configure adc interrupt (if required): ? clear adif bit ? select adc interrupt priority 3. start sampling. 4. wait the required acquisition time. 5. trigger acquisition end, start conversion: 6. wait for a/d conversion to complete, by either: ? waiting for the adc interrupt, or ? waiting for the done bit to get set. 7. read adc result buffer, clear adif if required. 19.3 selecting the conversion sequence several groups of control bits select the sequence in which the a/d connects inputs to the sample/hold channel, converts a channel, writes the buffer memory and generates interrupts. the sequence is controlled by the sampling clocks. the smpi bits select the number of acquisition/ conversion sequences that would be performed before an interrupt occurs. this can vary from 1 sample per interrupt to 16 samples per interrupt. the bufm bit will split the 16-word results buffer into two 8-word groups. writing to the 8-word buffers will be alternated on each interrupt event. use of the bufm bit will depend on how much time is available for the moving of the buffers after the interrupt. if the processor can quickly unload a full buffer within the time it takes to acquire and convert one channel, the bufm bit can be ? 0 ? and up to 16 conversions (cor- responding to the 16 input channels) may be done per interrupt. the processor will have one acquisition and conversion time to move the sixteen conversions. if the processor cannot unload the buffer within the acquisition and conversion time, the bufm bit should be ? 1 ?. for example, if sm pi<3:0> (adcon2<5:2>) = 0111 , then eight conversions will be loaded into 1/2 of the buffer, following which an interrupt occurs. the next eight conversions will be loaded into the other 1/2 of the buffer. the processor will have the entire time between interrupts to move the eight conversions. the alts bit can be used to alternate the inputs selected during the sampling sequence. the input multiplexer has two sets of sample inputs: mux a and mux b. if the alts bit is ? 0 ?, only the mux a inputs are selected for sampling. if the alts bit is ? 1 ? and smpi<3:0> = 0000 on the first sample/convert sequence, the mux a inputs are selected and on the next acquire/convert sequence, the mux b inputs are selected. the cscna bit (adcon2<10>) will allow the multi- plexer input to be alternately scanned across a selected number of analog inputs for the mux a group. the inputs are selected by the adcssl register. if a particular bit in the adcssl register is ? 1 ?, the corre- sponding input is selected. the inputs are always scanned from lower to higher numbered inputs, starting after each interrupt. if the number of inputs selected is greater than the number of samples taken per interrupt, the higher numbered inputs are unused.
? 2006 microchip technology inc. ds70117f-page 137 dspic30f6011/6012/6013/6014 19.4 programming the start of conversion trigger the conversion trigger will terminate acquisition and start the requested conversions. the ssrc<2:0> bits select the source of the conver- sion trigger. the ssrc bits provide for up to 4 alternate sources of conversion trigger. when ssrc<2:0> = 000 , the conversion trigger is under software control. clearing the samp bit will cause the conversion trigger. when ssrc<2:0> = 111 (auto-start mode), the con- version trigger is under a/d clock control. the samc bits select the number of a/d clocks between the start of acquisition and the start of conversion. this provides the fastest conversion rates on multiple channels. samc must always be at least 1 clock cycle. other trigger sources can come from timer modules or external interrupts. 19.5 aborting a conversion clearing the adon bit during a conversion will abort the current conversion and stop the sampling sequenc- ing until the next sampling trigger. the adcbuf will not be updated with the partially completed a/d conversion sample. that is, the adcbuf will continue to contain the value of the last completed conversion (or the last value written to the adcbuf register). if the clearing of the adon bit coincides with an auto- start, the clearing has a higher priority and a new conversion will not start. 19.6 selecting the adc conversion clock the adc conversion requires 14 t ad . the source of the adc conversion clock is software selected, using a six-bit counter. there are 64 possible options for t ad . equation 19-1: adc conversion clock the internal rc oscillator is selected by setting the adrc bit. for correct adc conversions, the adc conversion clock (t ad ) must be selected to ensure a minimum t ad time of 334 nsec (for v dd = 5v). refer to the electrical specifications section for minimum t ad under other operating conditions. example 19-1 shows a sample calculation for the adcs<5:0> bits, assuming a device operating speed of 30 mips. example 19-1: adc conversion clock and sampling rate calculation t ad = t cy * (0.5 * (adcs<5:0> + 1)) minimum t ad = 334 nsec adcs<5:0> = 2 ? 1 t ad t cy t cy = 33 .33 nsec (30 mips) = 2 ? ? 1 334 nsec 33.33 nsec = 19.04 therefore, set adcs<5:0> = 19 actual t ad = (adcs<5:0> + 1) t cy 2 = (19 + 1) 33.33 nsec 2 = 334 nsec if ssrc<2:0> = ?111? and samc<4:0> = ?00001? since, sampling time = acquisition time + conversion time = 1 t ad + 14 t ad = 15 x 334 nsec therefore, sampling rate = = ~200 khz 1 (15 x 334 nsec)
dspic30f6011/6012/6013/6014 ds70117f-page 138 ? 2006 microchip technology inc. 19.7 adc speeds the dspic30f 12-bit adc specifications permit a max- imum of 200 ksps sampling rate. the table below sum- marizes the conversion speeds for the dspic30f 12-bit adc and the required operating conditions. table 19-1: 12-bit adc extended conversion rates dspic30f 12-bit adc conversion rates speed t ad minimum sampling time min r s max v dd temperature channels configuration up to 200 ksps (1) 334 ns 1 t ad 2.5 k 4.5v to 5.5v -40c to +85c up to 100 ksps 668 ns 1 t ad 2.5 k 3.0v to 5.5v -40c to +125c note 1: external v ref - and v ref + pins must be used for correct operation. see figure 19-2 for recommended circuit. v ref -v ref + adc anx s/h ch x v ref -v ref + adc anx s/h ch x anx or v ref - or av ss or av dd
? 2006 microchip technology inc. ds70117f-page 139 dspic30f6011/6012/6013/6014 the following figure depicts the recommended circuit for the conversion rates above 200 ksps. the dspic30f6014 is shown as an example. figure 19-2: adc voltage reference schematic the configuration procedures below give the required setup values for the conversion speeds above 100 ksps. 19.7.1 200 ksps configuration guideline the following configuration items are required to achieve a 200 ksps conversion rate. ? comply with conditions provided in table 19-2. ? connect external v ref + and v ref - pins following the recommended circuit shown in figure 19-2. ? set ssrc<2.0> = 111 in the adcon1 register to enable the auto convert option. ? enable automatic sampling by setting the asam control bit in the adcon1 register. ? write the smpi<3.0> control bits in the adcon2 register for the desired number of conversions between interrupts. ? configure the adc clock period to be: by writing to the adcs<5:0> control bits in the adcon3 register. ? configure the sampling time to be 1 t ad by writing: samc<4:0> = 00001 . the following figure shows the timing diagram of the adc running at 200 ksps. the t ad selection in conjunc- tion with the guidelines described above allows a con- version speed of 200 ksps. see example 19-1 for code example. 72 74 73 v dd v ss 69 68 67 66 65 64 63 62 61 20 2 3 4 5 6 7 8 9 10 v ss v dd 13 14 15 16 50 49 v dd 47 46 45 44 21 41 40 39 38 37 36 35 34 v ref - v ref + av dd av ss 27 28 29 30 v ss v dd 33 17 18 19 75 1 57 56 55 54 53 52 v ss 60 59 58 43 42 76 78 77 79 22 80 dspic30f6014 v dd v dd v dd v dd v dd v dd v dd r2 10 c2 0.1 f c1 0.01 f r1 10 c8 1 f v dd c7 0.1 f v dd c6 0.01 f av dd c5 1 f av dd c4 0.1 f av dd c3 0.01 f see note 1: note 1: ensure adequate bypass capacitors are provided on each v dd pin. 1 (14 + 1) x 200,000 = 334 ns
dspic30f6011/6012/6013/6014 ds70117f-page 140 ? 2006 microchip technology inc. figure 19-3: converting 1 channel at 200 ksps, auto-sample start, 1 t ad sampling time t conv = 14 t ad t samp = 1 t ad t samp = 1 t ad adclk samp done adcbuf0 adcbuf1 instruction execution bset adcon1, asam t conv = 14 t ad
? 2006 microchip technology inc. ds70117f-page 141 dspic30f6011/6012/6013/6014 19.8 a/d acquisition requirements the analog input model of the 12-bit a/d converter is shown infigure 19-4. the total sampling time for the a/d is a function of the internal amplifier settling time and the holding capacitor charge time. for the a/d converter to meet its specified accuracy, the charge holding capacitor (c hold ) must be allowed to fully charge to the voltage level on the analog input pin. the source impedance (r s ), the interconnect impedance (r ic ), and the internal sampling switch (r ss ) impedance combine to directly affect the time required to charge the capacitor c hold . the combined impedance of the analog sources must therefore be small enough to fully charge the holding capacitor within the chosen sample time. to minimize the effects of pin leakage currents on the accuracy of the a/d con- verter, the maximum recommended source imped- ance, r s , is 2.5 k . after the analog input channel is selected (changed), this sampling function must be completed prior to starting the conversion. the internal holding capacitor will be in a discharged state prior to each sample operation. figure 19-4: 12-bit a/d converter analog input model c pin va rs anx v t = 0.6v v t = 0.6v i leakage r ic 250 sampling switch r ss c hold = dac capacitance v ss v dd = 18 pf 500 na legend: c pin v t i leakage r ic r ss c hold = input capacitance = threshold voltage = leakage current at the pin due to = interconnect resistance = sampling switch resistance = sample/hold capacitance (from dac) various junctions note: c pin value depends on device package and is not tested. effect of c pin negligible if rs 2.5 k . r ss 3 k
dspic30f6011/6012/6013/6014 ds70117f-page 142 ? 2006 microchip technology inc. 19.9 module power-down modes the module has 2 internal power modes. when the adon bit is ? 1 ?, the module is in active mode; it is fully powered and functional. when adon is ? 0 ?, the module is in off mode. the dig- ital and analog portions of the circuit are disabled for maximum current savings. in order to return to the active mode from off mode, the user must wait for the adc circuitry to stabilize. 19.10 adc operation during cpu sleep and idle modes 19.10.1 adc operation during cpu sleep mode when the device enters sleep mode, all clock sources to the module are shutdown and stay at logic ? 0 ?. if sleep occurs in the middle of a conversion, the con- version is aborted. the converter will not continue with a partially completed conversion on exit from sleep mode. register contents are not affected by the device entering or leaving sleep mode. the adc module can operate during sleep mode if the adc clock source is set to rc (adrc = 1 ). when the rc clock source is selected, the a/d module waits one instruction cycle before starting the conversion. this allows the sleep instruction to be executed which elim- inates all digital switching noise from the conversion. when the conversion is complete, the conv bit will be cleared and the result loaded into the adcbuf register. if the a/d interrupt is enabled, the device will wake-up from sleep. if the a/d interrupt is not enabled, the adc module will then be turned off, although the adon bit will remain set. 19.10.2 a/d operation during cpu idle mode the adsidl bit selects if the module will stop on idle or continue on idle. if adsidl = 0 , the module will con- tinue operation on assertion of idle mode. if adsidl = 1 , the module will stop on idle. 19.11 effects of a reset a device reset forces all registers to their reset state. this forces the adc module to be turned off, and any conversion and sampling sequence is aborted. the val- ues that are in the adcbuf registers are not modified. the a/d result register will contain unknown data after a power-on reset. 19.12 output formats the adc result is 12 bits wide. the data buffer ram is also 12 bits wide. the 12-bit data can be read in one of four different formats. the form<1:0> bits select the format. each of the output formats translates to a 16-bit result on the data bus. figure 19-5: adc output data formats ram contents: d11 d10 d09 d08 d07 d06 d05 d04 d03 d02 d01 d00 read to bus: signed fractional d11 d10d09d08d07d06d05d04d03d02d01d000000 fractional d11d10d09d08d07d06d05d04d03d02d01d000000 signed integer d11 d11 d11 d11 d11 d10 d09 d08 d07 d06 d05 d04 d03 d02 d01 d00 integer 0000d11d10d09d08d07d06d05d04d03d02d01d00
? 2006 microchip technology inc. ds70117f-page 143 dspic30f6011/6012/6013/6014 19.13 configuring analog port pins the use of the adpcfg and tris registers control the operation of the adc port pins. the port pins that are desired as analog inputs must have their correspond- ing tris bit set (input). if the tris bit is cleared (out- put), the digital output level (v oh or v ol ) will be converted. the adc operation is independent of the state of the ch0sa<3:0>/ch0sb<3:0> bits and the tris bits. when reading the port register, all pins configured as analog input channels will read as cleared. pins configured as digital inputs will not convert an ana- log input. analog levels on any pin that is defined as a digital input (including the anx pins) may cause the input buffer to consume current that exceeds the device specifications. 19.14 connection considerations the analog inputs have diodes to v dd and v ss as esd protection. this requires that the analog input be between v dd and v ss . if the input voltage exceeds this range by greater than 0.3v (either direction), one of the diodes becomes forward biased and it may damage the device if the input current specification is exceeded. an external rc filter is sometimes added for anti- aliasing of the input signal. the r component should be selected to ensure that the sampling time requirements are satisfied. any external components connected (via high impedance) to an analog input pin (capacitor, zener diode, etc.) should have very little leakage current at the pin.
dspic30f6011/6012/6013/6014 ds70117f-page 144 ? 2006 microchip technology inc. table 19-2: a/d converter register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state adcbuf0 0280 ? ? ? ? adc data buffer 0 0000 uuuu uuuu uuuu adcbuf1 0282 ? ? ? ? adc data buffer 1 0000 uuuu uuuu uuuu adcbuf2 0284 ? ? ? ? adc data buffer 2 0000 uuuu uuuu uuuu adcbuf3 0286 ? ? ? ? adc data buffer 3 0000 uuuu uuuu uuuu adcbuf4 0288 ? ? ? ? adc data buffer 4 0000 uuuu uuuu uuuu adcbuf5 028a ? ? ? ? adc data buffer 5 0000 uuuu uuuu uuuu adcbuf6 028c ? ? ? ? adc data buffer 6 0000 uuuu uuuu uuuu adcbuf7 028e ? ? ? ? adc data buffer 7 0000 uuuu uuuu uuuu adcbuf8 0290 ? ? ? ? adc data buffer 8 0000 uuuu uuuu uuuu adcbuf9 0292 ? ? ? ? adc data buffer 9 0000 uuuu uuuu uuuu adcbufa 0294 ? ? ? ? adc data buffer 10 0000 uuuu uuuu uuuu adcbufb 0296 ? ? ? ? adc data buffer 11 0000 uuuu uuuu uuuu adcbufc 0298 ? ? ? ? adc data buffer 12 0000 uuuu uuuu uuuu adcbufd 029a ? ? ? ? adc data buffer 13 0000 uuuu uuuu uuuu adcbufe 029c ? ? ? ? adc data buffer 14 0000 uuuu uuuu uuuu adcbuff 029e ? ? ? ? adc data buffer 15 0000 uuuu uuuu uuuu adcon1 02a0 adon ?adsidl ? ? ? form<1:0> ssrc<2:0> ? ? asam samp done 0000 0000 0000 0000 adcon2 02a2 vcfg<2:0> ? ? cscna ? ?bufs ? smpi<3:0> bufm alts 0000 0000 0000 0000 adcon3 02a4 ? ? ? samc<4:0> adrc ? adcs<5:0> 0000 0000 0000 0000 adchs 02a6 ? ? ? ch0nb ch0sb<3:0> ? ? ? ch0na ch0sa<3:0> 0000 0000 0000 0000 adpcfg 02a8 pcfg15 pcfg14 pcfg13 pcfg12 pcfg11 pcfg10 pcfg9 pcfg8 pcfg7 pcfg6 pcfg5 pcfg4 pcfg3 pcfg2 pcfg1 pcfg0 0000 0000 0000 0000 adcssl 02aa cssl15 cssl14 cssl13 cssl12 cssl11 cssl10 cssl9 cssl8 cssl7 cssl6 cssl5 cssl4 cssl3 cssl2 cssl1 cssl0 0000 0000 0000 0000 legend: u = uninitialized bit note: refer to ?dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
? 2006 microchip technology inc. ds70117f-page 145 dspic30f6011/6012/6013/6014 20.0 system integration there are several features intended to maximize sys- tem reliability, minimize cost through elimination of external components, provide power-saving operating modes and offer code protection: ? oscillator selection ? reset - power-on reset (por) - power-up timer (pwrt) - oscillator start-up timer (ost) - programmable brown-out reset (bor) ? watchdog timer (wdt) ? low-voltage detect ? power-saving modes (sleep and idle) ? code protection ? unit id locations ? in-circuit serial programming (icsp) dspic30f devices have a watchdog timer which is permanently enabled via the configuration bits or can be software controlled. it runs off its own rc oscillator for added reliability. there are two timers that offer necessary delays on power-up. one is the oscillator start-up timer (ost), intended to keep the chip in reset until the crystal oscillator is stable. the other is the power-up timer (pwrt) which provides a delay on power-up only, designed to keep the part in reset while the power supply stabilizes. with these two timers on-chip, most applications need no external reset circuitry. sleep mode is designed to offer a very low-current power-down mode. the user can wake-up from sleep through external reset, watchdog timer wake-up, or through an interrupt. several oscillator options are also made available to allow the part to fit a wide variety of applications. in the idle mode, the clock sources are still active but the cpu is shut off. the rc oscillator option saves system cost while the lp crystal option saves power. 20.1 oscillator system overview the dspic30f oscillator system has the following modules and features: ? various external and internal oscillator options as clock sources ? an on-chip pll to boost internal operating frequency ? a clock switching mechanism between various clock sources ? programmable clock postscaler for system power savings ? a fail-safe clock monitor (fscm) that detects clock failure and takes fail-safe measures ? clock control register (osccon) ? configuration bits for main oscillator selection table 20-1 provides a summary of the dspic30f oscil- lator operating modes. a simplified diagram of the oscillator system is shown in figure 20-1. configuration bits determine the clock source upon power-on reset (por) and brown-out reset (bor). thereafter, the clock source can be changed between permissible clock sources. the osccon register con- trols the clock switching and reflects system clock related status bits. note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157).
dspic30f6011/6012/6013/6014 ds70117f-page 146 ? 2006 microchip technology inc. table 20-1: oscillator operating modes oscillator mode description xtl 200 khz-4 mhz crystal on osc1:osc2. xt 4 mhz-10 mhz crystal on osc1:osc2. xt w/pll 4x 4 mhz-10 mhz crystal on osc1:osc2, 4x pll enabled. xt w/pll 8x 4 mhz-10 mhz crystal on osc1:osc2, 8x pll enabled. xt w/pll 16x 4 mhz-10 mhz crystal on osc1:osc2, 16x pll enabled (1) . lp 32 khz crystal on sosco:sosci (2) . hs 10 mhz-25 mhz crystal. ec external clock input (0-40 mhz). ecio external clock input (0-40 mhz), osc2 pin is i/o. ec w/pll 4x external clock input (4-10 mhz), osc2 pin is i/o, 4x pll enabled (1) . ec w/pll 8x external clock input (4-10 mhz), osc2 pin is i/o, 8x pll enabled (1) . ec w/pll 16x external clock input (4-7.5 mhz), osc2 pin is i/o, 16x pll enabled (1) . erc external rc oscillator, osc2 pin is f osc /4 output (3) . ercio external rc oscillator, osc2 pin is i/o (3) . frc 7.37 mhz internal rc oscillator. lprc 512 khz internal rc oscillator. note 1: dspic30f maximum operating frequency of 120 mhz must be met. 2: lp oscillator can be conveniently shared as system clock, as well as real-time clock for timer1. 3: requires external r and c. frequency operation up to 4 mhz.
? 2006 microchip technology inc. ds70117f-page 147 dspic30f6011/6012/6013/6014 figure 20-1: oscillator system block diagram primary osc1 osc2 sosco sosci oscillator 32 khz lp clock and control block switching oscillator x4, x8, x16 pll primary oscillator stability detector stability detector secondary oscillator programmable clock divider oscillator start-up timer fail-safe clock monitor (fscm) internal fast rc oscillator (frc) internal low power rc oscillator (lprc) pwrsav instruction wake-up request oscillator configuration bits system clock oscillator trap to timer1 lprc frc secondary osc por done primary osc f pll post<1:0> 2 fcksm<1:0> 2 pll lock cosc<1:0> nosc<1:0> oswen cf
dspic30f6011/6012/6013/6014 ds70117f-page 148 ? 2006 microchip technology inc. 20.2 oscillator configurations 20.2.1 initial clock source selection while coming out of power-on reset or brown-out reset, the device selects its clock source based on: a) fos<1:0> configuration bits that select one of four oscillator groups, b) and fpr<3:0> configuration bits that select one of 13 oscillator choices within the primary group. the selection is as shown in table 20-2. table 20-2: configuration bit values for clock selection 20.2.2 oscillator start-up timer (ost) in order to ensure that a crystal oscillator (or ceramic resonator) has started and stabilized, an oscillator start-up timer is included. it is a simple 10-bit counter that counts 1024 t osc cycles before releasing the oscillator clock to the rest of the system. the time-out period is designated as t ost . the t ost time is involved every time the oscillator has to restart (i.e., on por, bor and wake-up from sleep). the oscillator start-up timer is applied to the lp oscillator, xt, xtl, and hs modes (upon wake-up from sleep, por and bor) for the primary oscillator. 20.2.3 lp oscillator control enabling the lp oscillator is controlled with two elements: 1. the current oscillator group bits cosc<1:0>. 2. the lposcen bit (oscon register). the lp oscillator is on (even during sleep mode) if lposcen = 1. the lp oscillator is the device clock if: ? cosc<1:0> = 00 (lp selected as main oscillator) and ? lposcen = 1 keeping the lp oscillator on at all times allows for a fast switch to the 32 khz system clock for lower power oper- ation. returning to the faster main oscillator will still require a start-up time. oscillator mode oscillator source fos1 fos0 fpr3 fpr2 fpr1 fpr0 osc2 function ec primary 1 11011 clko ecio primary 1 11100 i/o ec w/ pll 4x primary 1 11101 i/o ec w/ pll 8x primary 1 11110 i/o ec w/ pll 16x primary 1 11111 i/o erc primary 1 11001 clko ercio primary 1 11000 i/o xt primary 1 10100 osc2 xt w/ pll 4x primary 1 10101 osc2 xt w/ pll 8x primary 1 10110 osc2 xt w/ pll 16x primary 1 10111 osc2 xtl primary 1 1000x osc2 hs primary 1 1001x osc2 lp secondary 0 0 ???? (notes 1, 2) frc internal frc 0 1 ???? (notes 1, 2) lprc internal lprc 1 0 ???? (notes 1, 2) note 1: osc2 pin function is determined by the primary oscillator mode selection (fpr<3:0>). 2: osc1 pin cannot be used as an i/o pin even if the secondary oscillator or an internal clock source is selected at all times.
? 2006 microchip technology inc. ds70117f-page 149 dspic30f6011/6012/6013/6014 20.2.4 phase locked loop (pll) the pll multiplies the clock which is generated by the primary oscillator. the pll is selectable to have either gains of x4, x8, and x16. input and output frequency ranges are summarized in table 20-3. table 20-3: pll frequency range the pll features a lock output which is asserted when the pll enters a phase locked state. should the loop fall out of lock (e.g., due to noise), the lock signal will be rescinded. the state of this signal is reflected in the read only lock bit in the osccon register. 20.2.5 fast rc oscillator (frc) the frc oscillator is a fast (7.37 mhz 2% nominal) internal rc oscillator. this oscillator is intended to pro- vide reasonable device operating speeds without the use of an external crystal, ceramic resonator, or rc network. the dspic30f operates from the frc oscillator when- ever the current oscillator selection control bits in the osccon register (cosc<13:12>) are set to ? 01 ?. the four bit field specified by tun<3:0> (osccon <15:14> and osccon<11:10>) allows the user to tune the internal fast rc oscillator (nominal 7.37mhz). the user can tune the frc oscillator within a range of -12% (or -960 khz) to +10.5% (or +840 khz) in steps of 1.50% around the factory-calibrated setting, see table 20-4. table 20-4: frc tuning 20.2.6 low power rc oscillator (lprc) the lprc oscillator is a component of the watchdog timer (wdt) and oscillates at a nominal frequency of 512 khz. the lprc oscillator is the clock source for the power-up timer (pwrt) circuit, wdt, and clock monitor circuits. it may also be used to provide a low frequency clock source option for applications where power consumption is critical and timing accuracy is not required the lprc oscillator is always enabled at a power-on reset because it is the clock source for the pwrt. after the pwrt expires, the lprc oscillator will remain on if one of the following is true: ? the fail-safe clock monitor is enabled ? the wdt is enabled ? the lprc oscillator is selected as the system clock via the cosc<1:0> control bits in the osccon register if one of the above conditions is not true, the lprc will shut off after the pwrt expires. 20.2.7 fail-safe clock monitor the fail-safe clock monitor (fscm) allows the device to continue to operate even in the event of an oscillator failure. the fscm function is enabled by appropriately programming the fcksm configuration bits (clock switch and monitor selection bits) in the fosc device configuration register. if the fscm function is enabled, the lprc internal oscillator will run at all times (except during sleep mode) and will not be subject to control by the swdten bit. in the event of an oscillator failure, the fscm will gen- erate a clock failure trap event and will switch the sys- tem clock over to the frc oscillator. the user will then have the option to either attempt to restart the oscillator or execute a controlled shutdown. the user may decide to treat the trap as a warm reset by simply loading the reset address into the oscillator fail trap vector. in this event, the cf (clock fail) status bit (osccon<3>) is also set whenever a clock failure is recognized. in the event of a clock failure, the wdt is unaffected and continues to run on the lprc clock. f in pll multiplier f out 4 mhz-10 mhz x4 16 mhz-40 mhz 4 mhz-10 mhz x8 32 mhz-80 mhz 4 mhz-7.5 mhz x16 64 mhz-120 mhz tun<3:0>bits frc frequency 0111 + 10.5% 0110 + 9.0% 0101 + 7.5% 0100 + 6.0% 0011 + 4.5% 0010 + 3.0% 0001 + 1.5% 0000 center frequency (oscillator is running at calibrated frequency) 1111 - 1.5% 1110 - 3.0% 1101 - 4.5% 1100 - 6.0% 1011 - 7.5% 1010 - 9.0% 1001 - 10.5% 1000 - 12.0% note 1: osc2 pin function is determined by the primary oscillator mode selection (fpr<3:0>). 2: osc1 pin cannot be used as an i/o pin even if the secondary oscillator or an internal clock source is selected at all times.
dspic30f6011/6012/6013/6014 ds70117f-page 150 ? 2006 microchip technology inc. if the oscillator has a very slow start-up time coming out of por, bor or sleep, it is possible that the pwrt timer will expire before the oscillator has started. in such cases, the fscm will be activated and the fscm will initiate a clock failure trap, and the cosc<1:0> bits are loaded with frc oscillator selection. this will effec- tively shut off the original oscillator that was trying to start. the user may detect this situation and restart the oscillator in the clock fail trap isr. upon a clock failure detection, the fscm module will initiate a clock switch to the frc oscillator as follows: 1. the cosc bits (osccon<13:12>) are loaded with the frc oscillator selection value. 2. cf bit is set (osccon<3>). 3. oswen control bit (osccon<0>) is cleared. for the purpose of clock switching, the clock sources are sectioned into four groups: 1. primary 2. secondary 3. internal frc 4. internal lprc the user can switch between these functional groups but cannot switch between options within a group. if the primary group is selected, then the choice within the group is always determined by the fpr<3:0> configuration bits. the osccon register holds the control and status bits related to clock switching. ? cosc<1:0>: read-only status bits always reflect the current oscillator group in effect. ? nosc<1:0>: control bits which are written to indicate the new oscillator group of choice. - on por and bor, cosc<1:0> and nosc<1:0> are both loaded with the configuration bit values fos<1:0>. ? lock: the lock status bit indicates a pll lock. ? cf: read only status bit indicating if a clock fail detect has occurred. ? oswen: control bit changes from a ? 0 ? to a ? 1 ? when a clock transition sequence is initiated. clearing the oswen control bit will abort a clock transition in progress (used for hang-up situations). if configuration bits fcksm<1:0> = 1x , then the clock switching and fail-safe clock monitoring functions are disabled. this is the default configuration bit setting. if clock switching is disabled, then the fos<1:0> and fpr<3:0> bits directly control the oscillator selection and the cosc<1:0> bits do not control the clock selec- tion. however, these bits will reflect the clock source selection. 20.2.8 protection against accidental writes to osccon a write to the osccon register is intentionally made difficult because it controls clock switching and clock scaling. to write to the osccon low byte, the following code sequence must be executed without any other instructions in between: byte write is allowed for one instruction cycle . write the desired value or use bit manipulation instruction. to write to the osccon high byte, the following instructions must be executed without any other instructions in between: byte write is allowed for one instruction cycle . write the desired value or use bit manipulation instruction. note: the application should not attempt to switch to a clock of frequency lower than 100 khz when the fail-safe clock monitor is enabled. if such clock switching is performed, the device may generate an oscillator fail trap and switch to the fast rc oscillator. byte write ?0x46? to osccon low byte write ?0x57? to osccon low byte write ? 0x78 ? to osccon high byte write ? 0x9a ? to osccon high
? 2006 microchip technology inc. ds70117f-page 151 dspic30f6011/6012/6013/6014 20.3 reset the dspic30f differentiates between various kinds of reset: a) power-on reset (por) b) mclr reset during normal operation c) mclr reset during sleep d) watchdog timer (wdt) reset (during normal operation) e) programmable brown-out reset (bor) f) reset instruction g) reset caused by trap lockup (trapr) h) reset caused by illegal opcode or by using an uninitialized w register as an address pointer (iopuwr) different registers are affected in different ways by var- ious reset conditions. most registers are not affected by a wdt wake-up since this is viewed as the resump- tion of normal operation. status bits from the rcon register are set or cleared differently in different reset situations, as indicated in table 20-5. these bits are used in software to determine the nature of the reset. a block diagram of the on-chip reset circuit is shown in figure 20-2. a mclr noise filter is provided in the mclr reset path. the filter detects and ignores small pulses. internally generated resets do not drive mclr pin low. figure 20-2: reset system block diagram 20.3.1 por: power-on reset a power-on event will generate an internal por pulse when a v dd rise is detected. the reset pulse will occur at the por circuit threshold voltage (v por ) which is nominally 1.85v. the device supply voltage character- istics must meet specified starting voltage and rise rate requirements. the por pulse will reset a por timer and place the device in the reset state. the por also selects the device clock source identified by the oscillator configuration fuses. the por circuit inserts a small delay, t por , which is nominally 10 s and ensures that the device bias cir- cuits are stable. furthermore, a user selected power- up time-out (t pwrt ) is applied. the t pwrt parameter is based on device configuration bits and can be 0 ms (no delay), 4 ms, 16 ms, or 64 ms. the total delay is at device power-up, t por + t pwrt . when these delays have expired, sysrst will be negated on the next leading edge of the q1 clock and the pc will jump to the reset vector. the timing for the sysrst signal is shown in figure 20-3 through figure 20-5. s r q mclr v dd v dd rise detect por sysrst sleep or idle brown-out reset boren reset instruction wdt module digital glitch filter bor trap conflict illegal opcode/ uninitialized w register
dspic30f6011/6012/6013/6014 ds70117f-page 152 ? 2006 microchip technology inc. figure 20-3: time-out sequence on power-up (mclr tied to v dd ) figure 20-4: time-out sequence on power-up (mclr not tied to v dd ): case 1 figure 20-5: time-out sequence on power-up (mclr not tied to v dd ): case 2 t pwrt t ost v dd internal por pwrt time-out ost time-out internal reset mclr t pwrt t ost v dd internal por pwrt time-out ost time-out internal reset mclr v dd mclr internal por pwrt time-out ost time-out internal reset t pwrt t ost
? 2006 microchip technology inc. ds70117f-page 153 dspic30f6011/6012/6013/6014 20.3.1.1 por with long crystal start-up time (with fscm enabled) the oscillator start-up circuitry is not linked to the por circuitry. some crystal circuits (especially low fre- quency crystals) will have a relatively long start-up time. therefore, one or more of the following conditions is possible after the por timer and the pwrt have expired: ? the oscillator circuit has not begun to oscillate. ? the oscillator start-up timer has not expired (if a crystal oscillator is used). ? the pll has not achieved a lock (if pll is used). if the fscm is enabled and one of the above conditions is true, then a clock failure trap will occur. the device will automatically switch to the frc oscillator and the user can switch to the desired crystal oscillator in the trap isr. 20.3.1.2 operating without fscm and pwrt if the fscm is disabled and the power-up timer (pwrt) is also disabled, then the device will exit rap- idly from reset on power-up. if the clock source is frc, lprc, extrc or ec, it will be active immediately. if the fscm is disabled and the system clock has not started, the device will be in a frozen state at the reset vector until the system clock starts. from the user?s perspective, the device will appear to be in reset until a system clock is available. 20.3.2 bor: programmable brown-out reset the bor (brown-out reset) module is based on an internal voltage reference circuit. the main purpose of the bor module is to generate a device reset when a brown-out condition occurs. brown-out conditions are generally caused by glitches on the ac mains (i.e., missing portions of the ac cycle waveform due to bad power transmission lines, or voltage sags due to exces- sive current draw when a large inductive load is turned on). the bor module allows selection of one of the following voltage trip points (see table 23-11): ?2.6v-2.71v ?4.1v-4.4v ? 4.58v-4.73v a bor will generate a reset pulse which will reset the device. the bor will select the clock source based on the device configuration bit values (fos<1:0> and fpr<3:0>). furthermore, if an oscillator mode is selected, the bor will activate the oscillator start-up timer (ost). the system clock is held until ost expires. if the pll is used, then the clock will be held until the lock bit (osccon<5>) is ? 1 ?. concurrently, the por time-out (t por ) and the pwrt time-out (t pwrt ) will be applied before the internal reset is released. if t pwrt = 0 and a crystal oscillator is being used, then a nominal delay of t fscm = 100 s is applied. the total delay in this case is (t por + t fscm ). the bor status bit (rcon<1>) will be set to indicate that a bor has occurred. the bor circuit, if enabled, will continue to operate while in sleep or idle modes and will reset the device should v dd fall below the bor threshold voltage. figure 20-6: external power-on reset circuit (for slow v dd power-up) note: the bor voltage trip points indicated here are nominal values provided for design guidance only. refer to the electrical specifications in the specific device data sheet for bor voltage limit specifications. note: dedicated supervisory devices, such as the mcp1xx and mcp8xx, may also be used as an external power-on reset circuit. note 1: external power-on reset circuit is required only if the v dd power-up slope is too slow. the diode d helps discharge the capacitor quickly when v dd powers down. 2: r should be suitably chosen so as to make sure that the voltage drop across r does not violate the device?s elec trical specifications. 3: r1 should be suitably chosen so as to limit any current flowing into mclr from external capacitor c, in the event of mclr /v pp pin breakdown due to elec trostatic discharge (esd), or electrical overstress (eos). c r1 r d v dd dspic30f mclr
dspic30f6011/6012/6013/6014 ds70117f-page 154 ? 2006 microchip technology inc. table 20-5 shows the reset conditions for the rcon register. since the control bits within the rcon register are r/w, the information in the table implies that all the bits are negated prior to the action specified in the condition column. table 20-5: initialization condition for rcon register: case 1 condition program counter trapr iopuwr extr swr wdto idle sleep por bor power-on reset 0x000000 0 0 0 0 0 0 0 1 1 brown-out reset 0x000000 0 0 0 0 0 0 0 0 1 mclr reset during normal operation 0x000000 0 0 1 0 0 0 0 0 0 software reset during normal operation 0x000000 0 0 0 1 0 0 0 0 0 mclr reset during sleep 0x000000 0 0 1 0 0 0 1 0 0 mclr reset during idle 0x000000 0 0 1 0 0 1 0 0 0 wdt time-out reset 0x000000 0 0 0 0 1 0 0 0 0 wdt wake-up pc + 2 0 0 0 0 1 0 1 0 0 interrupt wake-up from sleep pc + 2 (1) 000000100 clock failure trap 0x000004 0 0 0 0 0 0 0 0 0 trap reset 0x000000 1 0 0 0 0 0 0 0 0 illegal operation trap 0x000000 0 1 0 0 0 0 0 0 0 legend: u = unchanged, x = unknown note 1: when the wake-up is due to an enabled interrupt, the pc is loaded with the corresponding interrupt vector.
? 2006 microchip technology inc. ds70117f-page 155 dspic30f6011/6012/6013/6014 table 20-6 shows a second example of the bit conditions for the rcon register. in this case, it is not assumed the user has set/cleared specific bits prior to action specified in the condition column. table 20-6: initialization condition for rcon register: case 2 condition program counter trapr iopuwr extr swr wdto idle sleep por bor power-on reset 0x000000 0 0 0 0 0 0 0 1 1 brown-out reset 0x000000 u u u u u u u 0 1 mclr reset during normal operation 0x000000 u u 1 0 0 0 0 u u software reset during normal operation 0x000000 u u 0 1 0 0 0 u u mclr reset during sleep 0x000000 u u 1 u 0 0 1 u u mclr reset during idle 0x000000 u u 1 u 0 1 0 u u wdt time-out reset 0x000000 u u 0 0 1 0 0 u u wdt wake-up pc + 2 u u u u 1 u 1 u u interrupt wake-up from sleep pc + 2 (1) uuuuuu1uu clock failure trap 0x000004 u u u u u u u u u trap reset 0x000000 1 u u u u u u u u illegal operation reset 0x000000 u 1 u u u u u u u legend: u = unchanged note: when the wake-up is due to an enabled interrupt, the pc is loaded with the corresponding interrupt vector.
dspic30f6011/6012/6013/6014 ds70117f-page 156 ? 2006 microchip technology inc. 20.4 watchdog timer (wdt) 20.4.1 watchdog timer operation the primary function of the watchdog timer (wdt) is to reset the processor in the event of a software mal- function. the wdt is a free-running timer which runs off an on-chip rc oscillator, requiring no external com- ponent. therefore, the wdt timer will continue to oper- ate even if the main processor clock (e.g., the crystal oscillator) fails. 20.4.2 enabling and disabling the wdt the watchdog timer can be ?enabled? or ?disabled? only through a configuration bit (fwdten) in the configuration register, fwdt. setting fwdten = 1 enables the watchdog timer. the enabling is done when programming the device. by default, after chip erase, fwdten bit = 1 . any device programmer capable of programming dspic30f devices allows programming of this and other configuration bits. if enabled, the wdt will increment until it overflows or ?times out?. a wdt time-out will force a device reset (except during sleep). to prevent a wdt time-out, the user must clear the watchdog timer using a clrwdt instruction. if a wdt times out during sleep, the device will wake- up. the wdto bit in the rcon register will be cleared to indicate a wake-up resulting from a wdt time-out. setting fwdten = 0 allows user software to enable/ disable the watchdog timer via the swdten (rcon<5>) control bit. 20.5 low-voltage detect the low-voltage detect (lvd) module is used to detect when the v dd of the device drops below a threshold value, v lvd , which is determined by the lvdl<3:0> bits (rcon<11:8>) and is thus user pro- grammable. the internal voltage reference circuitry requires a nominal amount of time to stabilize, and the bgst bit (rcon<13>) indicates when the voltage reference has stabilized. in some devices, the lvd threshold voltage may be applied externally on the lvdin pin. the lvd module is enabled by setting the lvden bit (rcon<12>). 20.6 power saving modes there are two power-saving states that can be entered through the execution of a special instruction, pwrsav . these are sleep and idle. the format of the pwrsav instruction is as follows: pwrsav , where ? parameter ? defines idle or sleep mode. 20.6.1 sleep mode in sleep mode, the clock to the cpu and peripherals is shutdown. if an on-chip oscillator is being used, it is shutdown. the fail-safe clock monitor is not functional during sleep since there is no clock to monitor. however, lprc clock remains active if wdt is operational during sleep. the brown-out protection circuit and the low-voltage detect circuit, if enabled, will remain functional during sleep. the processor wakes up from sleep if at least one of the following conditions has occurred: ? any interrupt that is individually enabled and meets the required priority level ? any reset (por, bor and mclr ) ? wdt time-out on waking up from sleep mode, the processor will restart the same clock that was active prior to entry into sleep mode. when clock switching is enabled, bits cosc<1:0> will determine the oscillator source that will be used on wake-up. if clock switch is disabled, then there is only one system clock. if the clock source is an oscillator, the clock to the device will be held off until ost times out (indicating a stable oscillator). if pll is used, the system clock is held off until lock = 1 (indicating that the pll is stable). in either case, t por , t lock and t pwrt delays are applied. if ec, frc, lprc or extrc oscillators are used, then a delay of t por (~ 10 s) is applied. this is the smallest delay possible on wake-up from sleep. moreover, if lp oscillator was active during sleep and lp is the oscillator used on wake-up, then the start-up delay will be equal to t por . pwrt delay and ost timer delay are not applied. in order to have -the small- est possible start-up delay when waking up from sleep, one of these faster wake-up options should be selected before entering sleep. note: if a por or bor occurred, the selection of the oscillator is based on the fos<1:0> and fpr<3:0> configuration bits.
? 2006 microchip technology inc. ds70117f-page 157 dspic30f6011/6012/6013/6014 any interrupt that is individually enabled (using the cor- responding ie bit) and meets the prevailing priority level will be able to wake-up the processor. the processor will process the interrupt and branch to the isr. the sleep status bit in the rcon register is set upon wake-up. all resets will wake-up the processor from sleep mode. any reset, other than por, will set the sleep status bit. in a por, the sleep bit is cleared. if the watchdog timer is enabled, then the processor will wake-up from sleep mode upon wdt time-out. the sleep and wdto status bits are both set. 20.6.2 idle mode in idle mode, the clock to the cpu is shutdown while peripherals keep running. unlike sleep mode, the clock source remains active. several peripherals have a control bit in each module that allows them to operate during idle. lprc fail-safe clock remains active if clock failure detect is enabled. the processor wakes up from idle if at least one of the following conditions has occurred: ? any interrupt that is individually enabled (ie bit is ? 1 ?) and meets the required priority level ? any reset (por, bor, mclr ) ? wdt time-out upon wake-up from idle mode, the clock is re-applied to the cpu and instruction execution begins immedi- ately, starting with the instruction following the pwrsav instruction. any interrupt that is individually enabled (using ie bit) and meets the prevailing priority level will be able to wake-up the processor. the processor will process the interrupt and branch to the isr. the idle status bit in the rcon register is set upon wake-up. any reset other than por will set the idle status bit. on a por, the idle bit is cleared. if watchdog timer is enabled, then the processor will wake-up from idle mode upon wdt time-out. the idle and wdto status bits are both set. unlike wake-up from sleep, there are no time delays involved in wake-up from idle. 20.7 device configuration registers the configuration bits in each device configuration reg- ister specify some of the device modes and are programmed by a device programmer, or by using the in-circuit serial programming (icsp) feature of the device. each device configuration register is a 24-bit register, but only the lower 16 bits of each register are used to hold configuration data. there are four device configuration registers available to the user: 1. f osc (0xf80000): oscillator configuration register 2. fwdt (0xf80002): watchdog timer configuration register 3. fborpor (0xf80004): bor and por configuration register 4. fgs (0xf8000a): general code segment configuration register the placement of the configuration bits is automati- cally handled when you select the device in your device programmer. the desired state of the configuration bits may be specified in the source code (dependent on the language tool used), or through the programming inter- face. after the device has been programmed, the appli- cation software may read the configuration bit values through the table read instructions. for additional infor- mation, please refer to the programming specifications of the device. note: in spite of various delays applied (t por , t lock and t pwrt ), the crystal oscillator (and pll) may not be active at the end of the time-out (e.g., for low-frequency crys- tals). in such cases, if fscm is enabled, then the device will detect this as a clock failure and process the clock failure trap, the frc oscillator will be enabled and the user will have to re-enable the crystal oscillator. if fscm is not enabled, then the device will simply suspend execution of code until the clock is stable and will remain in sleep until the oscillator clock has started. note: if the code protection configuration fuse bits (fgs and fgs) have been programmed, an erase of the entire code-protected device is only possible at voltages v dd 4.5v.
dspic30f6011/6012/6013/6014 ds70117f-page 158 ? 2006 microchip technology inc. 20.8 peripheral module disable (pmd) registers the peripheral module disable (pmd) registers pro- vide a method to disable a peripheral module by stop- ping all clock sources supplied to that module. when a peripheral is disabled via the appropriate pmd control bit, the peripheral is in a minimum power consumption state. the control and status registers associated with the peripheral will also be disabled so writes to those registers will have no effect and read values will be invalid. a peripheral module will only be enabled if both the associated bit in the pmd register is cleared and the peripheral is supported by the specific dspic dsc vari- ant. if the peripheral is present in the device, it is enabled in the pmd register by default. 20.9 in-circuit debugger when mplab ? icd2 is selected as a debugger, the in- circuit debugging functionality is enabled. this function allows simple debugging functions when used with mplab ide. when the device has this feature enabled, some of the resources are not available for general use. these resources include the first 80 bytes of data ram and two i/o pins. one of four pairs of debug i/o pins may be selected by the user using configuration options in mplab ide. these pin pairs are named emud/emuc, emud1/ emuc1, emud2/emuc2 and emud3/emuc3. in each case, the selected emud pin is the emulation/ debug data line, and the emuc pin is the emulation/ debug clock line. these pins will interface to the mplab icd 2 module available from microchip. the selected pair of debug i/o pins is used by mplab icd 2 to send commands and receive responses, as well as to send and receive data. to use the in-circuit debugger function of the device, the design must imple- ment icsp connections to mclr , v dd , v ss , pgc, pgd, and the selected emudx/emucx pin pair. this gives rise to two possibilities: 1. if emud/emuc is selected as the debug i/o pin pair, then only a 5-pin interface is required, as the emud and emuc pin functions are multi- plexed with the pgd and pgc pin functions in all dspic30f devices. 2. if emud1/emuc1, emud2 /emuc2 or emud3/ emuc3 is selected as the debug i/o pin pair, then a 7-pin interface is required, as the emudx/emucx pin functions (x = 1, 2 or 3) are not multiplexed with the pgd and pgc pin functions. note: if a pmd bit is set, the corresponding mod- ule is disabled after a delay of 1 instruction cycle. similarly, if a pmd bit is cleared, the corresponding module is enabled after a delay of 1 instruction cycle (assuming the module control registers are already configured to enable module operation). note: in the dspic30f6011 and dspic30f6013 devices, the dcimd bit is readable and writable, and will be read as ? 1 ? when set.
? 2006 microchip technology inc. ds70117f-page 159 dspic30f6011/6012/6013/6014 table 20-7: system integration register map table 20-8: device configuration register map sfr name addr. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset state rcon 0740 trapr iopuwr bgst lvden lvdl<3:0> extr swr swdten wdto sleep idle bor por (note 1) osccon 0742 tun3 tun2 cosc<1:0> tun1 tun0 nosc<1:0> post<1:0> lock ?cf ? lposcen oswen (note 2) pmd1 0770 t5md t4md t3md t2md t1md ? ? dcimd i2cmd u2md u1md spi2md spi1md c2md c1md adcmd 0000 0000 0000 0000 pmd2 0772 ic8md ic7md ic6md ic5md ic4md ic3md ic2md ic1md oc8md oc7md oc6md oc5md oc4md oc3md oc2md oc1md 0000 0000 0000 0000 note 1: reset state depends on type of reset. 2: reset state depends on configuration bits. 3: refer to ?dspic30f family reference manual? (ds70046) for descriptions of register bit fields. file name addr. bits 23-16 bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 fosc f80000 ? fcksm<1:0> ? ? ? ? fos<1:0> ? ? ? ?fpr<3:0> fwdt f80002 ?fwdten ? ? ? ? ? ? ? ? ? fwpsa<1:0> fwpsb<3:0> fborpor f80004 ? mclren ? ? ? ? ? ? ?boren ? borv<1:0> ? ?fpwrt<1:0> fgs f8000a ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? gcp gwrp note: refer to ?dspic30f family reference manual? (ds70046) for descriptions of register bit fields.
dspic30f6011/6012/6013/6014 ds70117f-page 160 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 161 dspic30f6011/6012/6013/6014 21.0 instruction set summary the dspic30f instruction set adds many enhancements to the previous pic ? mcu instruction sets, while maintaining an easy migration from pic mcu instruction sets. most instructions are a single program memory word (24 bits). only three instructions require two program memory locations. each single word instruction is a 24-bit word divided into an 8-bit opcode which specifies the instruction type, and one or more operands which further specify the operation of the instruction. the instruction set is highly orthogonal and is grouped into five basic categories: ? word or byte-oriented operations ? bit-oriented operations ? literal operations ? dsp operations ? control operations table 21-1 shows the general symbols used in describing the instructions. the dspic30f instruction set summary in table 21-2 lists all the instructions, along with the status flags affected by each instruction. most word or byte-oriented w register instructions (including barrel shift instructions) have three operands: ? the first source operand which is typically a register ?wb? without any address modifier ? the second source operand which is typically a register ?ws? with or without an address modifier ? the destination of the result which is typically a register ?wd? with or without an address modifier however, word or byte-oriented file register instructions have two operands: ? the file register specified by the value ?f? ? the destination, which could either be the file register ?f? or the w0 register, which is denoted as ?wreg? most bit-oriented instructions (including simple rotate/ shift instructions) have two operands: ? the w register (with or without an address modifier) or file register (specified by the value of ?ws? or ?f?) ? the bit in the w register or file register (specified by a literal value or indirectly by the contents of register ?wb?) the literal instructions that involve data movement may use some of the following operands: ? a literal value to be loaded into a w register or file register (specified by the value of ?k?) ? the w register or file register where the literal value is to be loaded (specified by ?wb? or ?f?) however, literal instructions that involve arithmetic or logical operations use some of the following operands: ? the first source operand which is a register ?wb? without any address modifier ? the second source operand which is a literal value ? the destination of the result (only if not the same as the first source operand) which is typically a register ?wd? with or without an address modifier the mac class of dsp instructions may use some of the following operands: ? the accumulator (a or b) to be used (required operand) ? the w registers to be used as the two operands ? the x and y address space prefetch operations ? the x and y address space prefetch destinations ? the accumulator write back destination the other dsp instructions do not involve any multiplication, and may include: ? the accumulator to be used (required) ? the source or destination operand (designated as wso or wdo, respectively) with or without an address modifier ? the amount of shift specified by a w register ?wn? or a literal value the control instructions may use some of the following operands: ? a program memory address ? the mode of the table read and table write instructions note: this data sheet summarizes features of this group of dspic30f devices and is not intended to be a complete reference source. for more information on the cpu, peripherals, register descriptions and general device functionality, refer to the ? dspic30f family reference manual ? (ds70046). for more information on the device instruction set and programming, refer to the ? dspic30f/ 33f programmer?s reference manual? (ds70157).
dspic30f6011/6012/6013/6014 ds70117f-page 162 ? 2006 microchip technology inc. all instructions are a single word, except for certain double-word instructions, which were made double- word instructions so that all the required information is available in these 48 bits. in the second word, the 8msbs are ? 0 ?s. if this second word is executed as an instruction (by itself), it will execute as a nop . most single-word instructions are executed in a single instruction cycle, unless a conditional test is true or the program counter is changed as a result of the instruc- tion. in these cases, the execution takes two instruction cycles with the additional instruction cycle(s) executed as a nop . notable exceptions are the bra (uncondi- tional/computed branch), indirect call/goto , all table reads and writes, and return/retfie instructions, which are single-word instructions but take two or three cycles. certain instructions that involve skipping over the subsequent instruction require either two or three cycles if the skip is performed, depending on whether the instruction being skipped is a single word or two- word instruction. moreover, double-word moves require two cycles. the double-word instructions execute in two instruction cycles. note: for more details on the instruction set, refer to the ?dspic30f/33f programmer?s reference manual? (ds70157) table 21-1: symbols used in opcode descriptions field description #text means literal defined by ? text ? (text) means ?content of text ? [text] means ?the location addressed by text ? { } optional field or operation register bit field .b byte mode selection .d double-word mode selection .s shadow register select .w word mode selection (default) acc one of two accumulators {a, b} awb accumulator write back destination address register {w13, [w13]+=2} bit4 4-bit bit selection field (used in word addressed instructions) {0...15} c, dc, n, ov, z mcu status bits: carry, digit carry, negative, overflow, sticky zero expr absolute address, label or expression (resolved by the linker) f file register address {0x0000...0x1fff} lit1 1-bit unsigned literal {0,1} lit4 4-bit unsigned literal {0...15} lit5 5-bit unsigned literal {0...31} lit8 8-bit unsigned literal {0...255} lit10 10-bit unsigned literal {0...255} for byte mode, {0:1023} for word mode lit14 14-bit unsigned literal {0...16384} lit16 16-bit unsigned literal {0...65535} lit23 23-bit unsigned literal {0...8388608}; lsb must be 0 none field does not require an entry, may be blank oa, ob, sa, sb dsp status bits: acca overflow, accb overflow, acca saturate, accb saturate pc program counter slit10 10-bit signed literal {-512...511} slit16 16-bit signed literal {-32768...32767} slit6 6-bit signed literal {-16...16}
? 2006 microchip technology inc. ds70117f-page 163 dspic30f6011/6012/6013/6014 wb base w register {w0..w15} wd destination w register { wd, [wd], [wd++], [wd--], [++wd], [--wd] } wdo destination w register { wnd, [wnd], [wnd++], [wnd--], [++wnd], [--wnd], [wnd+wb] } wm,wn dividend, divisor working r egister pair (direct addressing) wm*wm multiplicand and multiplier working register pair for square instructions {w4 * w4,w5 * w5,w6 * w6,w7 * w7} wm*wn multiplicand and multiplier working register pair for dsp instructions {w4 * w5,w4 * w6,w4 * w7,w5 * w6,w5 * w7,w6 * w7} wn one of 16 working registers {w0..w15} wnd one of 16 destination working registers {w0..w15} wns one of 16 source working registers {w0..w15} wreg w0 (working register used in file register instructions) ws source w register { ws, [ws], [ws++], [ws--], [++ws], [--ws] } wso source w register { wns, [wns], [wns++], [wns--], [++wns], [--wns], [wns+wb] } wx x data space prefetch address register for dsp instructions {[w8] + = 6, [w8] + = 4, [w8] + = 2, [w8], [w8] - = 6, [w8] - = 4, [w8] - = 2, [w9] + = 6, [w9] + = 4, [w9] + = 2, [w9], [w9] - = 6, [w9] - = 4, [w9] - = 2, [w9 + w12],none} wxd x data space prefetch destination register for dsp instructions {w4..w7} wy y data space prefetch address register for dsp instructions {[w10] + = 6, [w10] + = 4, [w10] + = 2, [w10], [w10] - = 6, [w10] - = 4, [w10] - = 2, [w11] + = 6, [w11] + = 4, [w11] + = 2, [w11], [w11] - = 6, [w11] - = 4, [w11] - = 2, [w11 + w12], none} wyd y data space prefetch destination register for dsp instructions {w4..w7} table 21-1: symbols used in opcode descriptions (continued) field description
dspic30f6011/6012/6013/6014 ds70117f-page 164 ? 2006 microchip technology inc. table 21-2: instruction set overview base instr # assembly mnemonic assembly syntax description # of words # of cycles status flags affected 1 add add acc add accumulators 1 1 oa,ob,sa,sb add f f = f + wreg 1 1 c,dc,n,ov,z add f,wreg wreg = f + wreg 1 1 c,dc,n,ov,z add #lit10,wn wd = lit10 + wd 1 1 c,dc,n,ov,z add wb,ws,wd wd = wb + ws 1 1 c,dc,n,ov,z add wb,#lit5,wd wd = wb + lit5 1 1 c,dc,n,ov,z add wso,#slit4,acc 16-bit signed add to accumulator 1 1 oa,ob,sa,sb 2 addc addc f f = f + wreg + (c) 1 1 c,dc,n,ov,z addc f,wreg wreg = f + wreg + (c) 1 1 c,dc,n,ov,z addc #lit10,wn wd = lit10 + wd + (c) 1 1 c,dc,n,ov,z addc wb,ws,wd wd = wb + ws + (c) 1 1 c,dc,n,ov,z addc wb,#lit5,wd wd = wb + lit5 + (c) 1 1 c,dc,n,ov,z 3 and and f f = f .and. wreg 1 1 n,z and f,wreg wreg = f .and. wreg 1 1 n,z and #lit10,wn wd = lit10 .and. wd 1 1 n,z and wb,ws,wd wd = wb .and. ws 1 1 n,z and wb,#lit5,wd wd = wb .and. lit5 1 1 n,z 4 asr asr f f = arithmetic right shift f 1 1 c,n,ov,z asr f,wreg wreg = arithmetic right shift f 1 1 c,n,ov,z asr ws,wd wd = arithmetic right shift ws 1 1 c,n,ov,z asr wb,wns,wnd wnd = arithmetic right shift wb by wns 1 1 n,z asr wb,#lit5,wnd wnd = arithmetic right shift wb by lit5 1 1 n,z 5 bclr bclr f,#bit4 bit clear f 1 1 none bclr ws,#bit4 bit clear ws 1 1 none 6 bra bra c,expr branch if carry 1 1 (2) none bra ge,expr branch if greater than or equal 1 1 (2) none bra geu,expr branch if unsigned greater than or equal 1 1 (2) none bra gt,expr branch if greater than 1 1 (2) none bra gtu,expr branch if unsigned greater than 1 1 (2) none bra le,expr branch if less than or equal 1 1 (2) none bra leu,expr branch if unsigned less than or equal 1 1 (2) none bra lt,expr branch if less than 1 1 (2) none bra ltu,expr branch if unsigned less than 1 1 (2) none bra n,expr branch if negative 1 1 (2) none bra nc,expr branch if not carry 1 1 (2) none bra nn,expr branch if not negative 1 1 (2) none bra nov,expr branch if not overflow 1 1 (2) none bra nz,expr branch if not zero 1 1 (2) none bra oa,expr branch if accumulator a overflow 1 1 (2) none bra ob,expr branch if accumulator b overflow 1 1 (2) none bra ov,expr branch if overflow 1 1 (2) none bra sa,expr branch if accumulator a saturated 1 1 (2) none bra sb,expr branch if accumulator b saturated 1 1 (2) none bra expr branch unconditionally 1 2 none bra z,expr branch if zero 1 1 (2) none bra wn computed branch 1 2 none 7 bset bset f,#bit4 bit set f 1 1 none bset ws,#bit4 bit set ws 1 1 none 8 bsw bsw.c ws,wb write c bit to ws 1 1 none bsw.z ws,wb write z bit to ws 1 1 none
? 2006 microchip technology inc. ds70117f-page 165 dspic30f6011/6012/6013/6014 9 btg btg f,#bit4 bit toggle f 1 1 none btg ws,#bit4 bit toggle ws 1 1 none 10 btsc btsc f,#bit4 bit test f, skip if clear 1 1 (2 or 3) none btsc ws,#bit4 bit test ws, skip if clear 1 1 (2 or 3) none 11 btss btss f,#bit4 bit test f, skip if set 1 1 (2 or 3) none btss ws,#bit4 bit test ws, skip if set 1 1 (2 or 3) none 12 btst btst f,#bit4 bit test f 1 1 z btst.c ws,#bit4 bit test ws to c 1 1 c btst.z ws,#bit4 bit test ws to z 1 1 z btst.c ws,wb bit test ws to c 1 1 c btst.z ws,wb bit test ws to z 1 1 z 13 btsts btsts f,#bit4 bit test then set f 1 1 z btsts.c ws,#bit4 bit test ws to c, then set 1 1 c btsts.z ws,#bit4 bit test ws to z, then set 1 1 z 14 call call lit23 call subroutine 2 2 none call wn call indirect subroutine 1 2 none 15 clr clr f f = 0x0000 1 1 none clr wreg wreg = 0x0000 1 1 none clr ws ws = 0x0000 1 1 none clr acc,wx,wxd,wy,wyd,awb clear accumulator 1 1 oa,ob,sa,sb 16 clrwdt clrwdt clear watchdog timer 1 1 wdto,sleep 17 com com f f = f 11 n,z com f,wreg wreg = f 11 n,z com ws,wd wd = ws 11 n,z 18 cp cp f compare f with wreg 1 1 c,dc,n,ov,z cp wb,#lit5 compare wb with lit5 1 1 c,dc,n,ov,z cp wb,ws compare wb with ws (wb - ws) 1 1 c,dc,n,ov,z 19 cp0 cp0 f compare f with 0x0000 1 1 c,dc,n,ov,z cp0 ws compare ws with 0x0000 1 1 c,dc,n,ov,z 20 cpb cpb f compare f with wreg, with borrow 1 1 c,dc,n,ov,z cpb wb,#lit5 compare wb with lit5, with borrow 1 1 c,dc,n,ov,z cpb wb,ws compare wb with ws, with borrow (wb - ws - c ) 1 1 c,dc,n,ov,z 21 cpseq cpseq wb, wn compare wb with wn, skip if = 1 1 (2 or 3) none 22 cpsgt cpsgt wb, wn compare wb with wn, skip if > 1 1 (2 or 3) none 23 cpslt cpslt wb, wn compare wb with wn, skip if < 1 1 (2 or 3) none 24 cpsne cpsne wb, wn compare wb with wn, skip if 11 (2 or 3) none 25 daw daw wn wn = decimal adjust wn 1 1 c 26 dec dec f f = f -1 1 1 c,dc,n,ov,z dec f,wreg wreg = f -1 1 1 c,dc,n,ov,z dec ws,wd wd = ws - 1 1 1 c,dc,n,ov,z 27 dec2 dec2 f f = f -2 1 1 c,dc,n,ov,z dec2 f,wreg wreg = f -2 1 1 c,dc,n,ov,z dec2 ws,wd wd = ws - 2 1 1 c,dc,n,ov,z 28 disi disi #lit14 disable interrupts for k instruction cycles 1 1 none table 21-2: instruction set overview (continued) base instr # assembly mnemonic assembly syntax description # of words # of cycles status flags affected
dspic30f6011/6012/6013/6014 ds70117f-page 166 ? 2006 microchip technology inc. 29 div div.s wm,wn signed 16/16-bit integer divide 1 18 n,z,c,ov div.sd wm,wn signed 32/16-bit integer divide 1 18 n,z,c,ov div.u wm,wn unsigned 16/16-bit integer divide 1 18 n,z,c,ov div.ud wm,wn unsigned 32/16-bit integer divide 1 18 n,z,c,ov 30 divf divf wm,wn signed 16/16-bit fractional divide 1 18 n,z,c,ov 31 do do #lit14,expr do code to pc+expr, lit14+1 times 2 2 none do wn,expr do code to pc+expr, (wn)+1 times 2 2 none 32 ed ed wm*wm,acc,wx,wy,wxd euclidean distance (no accumulate) 1 1 oa,ob,oab, sa,sb,sab 33 edac edac wm*wm,acc,wx,wy,wxd euclidean distance 1 1 oa,ob,oab, sa,sb,sab 34 exch exch wns,wnd swap wns with wnd 1 1 none 35 fbcl fbcl ws,wnd find bit change from left (msb) side 1 1 c 36 ff1l ff1l ws,wnd find first one from left (msb) side 1 1 c 37 ff1r ff1r ws,wnd find first one from right (lsb) side 1 1 c 38 goto goto expr go to address 2 2 none goto wn go to indirect 1 2 none 39 inc inc f f = f + 1 1 1 c,dc,n,ov,z inc f,wreg wreg = f + 1 1 1 c,dc,n,ov,z inc ws,wd wd = ws + 1 1 1 c,dc,n,ov,z 40 inc2 inc2 f f = f + 2 1 1 c,dc,n,ov,z inc2 f,wreg wreg = f + 2 1 1 c,dc,n,ov,z inc2 ws,wd wd = ws + 2 1 1 c,dc,n,ov,z 41 ior ior f f = f .ior. wreg 1 1 n,z ior f,wreg wreg = f .ior. wreg 1 1 n,z ior #lit10,wn wd = lit10 .ior. wd 1 1 n,z ior wb,ws,wd wd = wb .ior. ws 1 1 n,z ior wb,#lit5,wd wd = wb .ior. lit5 1 1 n,z 42 lac lac wso,#slit4,acc load accumulator 1 1 oa,ob,oab, sa,sb,sab 43 lnk lnk #lit14 link frame pointer 1 1 none 44 lsr lsr f f = logical right shift f 1 1 c,n,ov,z lsr f,wreg wreg = logical right shift f 1 1 c,n,ov,z lsr ws,wd wd = logical right shift ws 1 1 c,n,ov,z lsr wb,wns,wnd wnd = logical right shift wb by wns 1 1 n,z lsr wb,#lit5,wnd wnd = logical right shift wb by lit5 1 1 n,z 45 mac mac wm*wn,acc,wx,wxd,wy,wyd , awb multiply and accumulate 1 1 oa,ob,oab, sa,sb,sab mac wm*wm,acc,wx,wxd,wy,wyd square and accumulate 1 1 oa,ob,oab, sa,sb,sab 46 mov mov f,wn move f to wn 1 1 none mov f move f to f 1 1 n,z mov f,wreg move f to wreg 1 1 n,z mov #lit16,wn move 16-bit literal to wn 1 1 none mov.b #lit8,wn move 8-bit literal to wn 1 1 none mov wn,f move wn to f 1 1 none mov wso,wdo move ws to wd 1 1 none mov wreg,f move wreg to f 1 1 n,z mov.d wns,wd move double from w(ns):w(ns+1) to wd 1 2 none mov.d ws,wnd move double from ws to w(nd+1):w(nd) 1 2 none 47 movsac movsac acc,wx,wxd,wy,wyd,awb prefetch and store accumulator 1 1 none table 21-2: instruction set overview (continued) base instr # assembly mnemonic assembly syntax description # of words # of cycles status flags affected
? 2006 microchip technology inc. ds70117f-page 167 dspic30f6011/6012/6013/6014 48 mpy mpy wm*wn,acc,wx,wxd,wy,wyd multiply wm by wn to accumulator 1 1 oa,ob,oab, sa,sb,sab mpy wm*wm,acc,wx,wxd,wy,wyd square wm to accumulator 1 1 oa,ob,oab, sa,sb,sab 49 mpy.n mpy.n wm*wn,acc,wx,wxd,wy,wyd -(multiply wm by wn) to accumulator 1 1 none 50 msc msc wm*wm,acc,wx,wxd,wy,wyd , awb multiply and subtract from accumulator 1 1 oa,ob,oab, sa,sb,sab 51 mul mul.ss wb,ws,wnd {wnd+1, wnd} = signed(wb) * signed(ws) 1 1 none mul.su wb,ws,wnd {wnd+1, wnd} = signed(wb) * unsigned(ws) 1 1 none mul.us wb,ws,wnd {wnd+1, wnd} = unsigned(wb) * signed(ws) 1 1 none mul.uu wb,ws,wnd {wnd+1, wnd} = unsigned(wb) * unsigned(ws) 11 none mul.su wb,#lit5,wnd {wnd+1, wnd} = signed(wb) * unsigned(lit5) 1 1 none mul.uu wb,#lit5,wnd {wnd+1, wnd} = unsigned(wb) * unsigned(lit5) 11 none mul f w3:w2 = f * wreg 1 1 none 52 neg neg acc negate accumulator 1 1 oa,ob,oab, sa,sb,sab neg f f = f + 1 1 1 c,dc,n,ov,z neg f,wreg wreg = f + 1 1 1 c,dc,n,ov,z neg ws,wd wd = ws + 1 1 1 c,dc,n,ov,z 53 nop nop no operation 1 1 none nopr no operation 1 1 none 54 pop pop f pop f from top-of-stack (tos) 1 1 none pop wdo pop from top-of-stack (tos) to wdo 1 1 none pop.d wnd pop from top-of-stack (tos) to w(nd):w(nd+1) 12 none pop.s pop shadow registers 1 1 all 55 push push f push f to top-of-stack (tos) 1 1 none push wso push wso to top-of-stack (tos) 1 1 none push.d wns push w(ns):w(ns+1) to top-of-stack (tos) 1 2 none push.s push shadow registers 1 1 none 56 pwrsav pwrsav #lit1 go into sleep or idle mode 1 1 wdto,sleep 57 rcall rcall expr relative call 1 2 none rcall wn computed call 1 2 none 58 repeat repeat #lit14 repeat next instruction lit14+1 times 1 1 none repeat wn repeat next instruction (wn)+1 times 1 1 none 59 reset reset software device reset 1 1 none 60 retfie retfie return from interrupt 1 3 (2) none 61 retlw retlw #lit10,wn return with literal in wn 1 3 (2) none 62 return return return from subroutine 1 3 (2) none 63 rlc rlc f f = rotate left through carry f 1 1 c,n,z rlc f,wreg wreg = rotate left through carry f 1 1 c,n,z rlc ws,wd wd = rotate left through carry ws 1 1 c,n,z 64 rlnc rlnc f f = rotate left (no carry) f 1 1 n,z rlnc f,wreg wreg = rotate left (no carry) f 1 1 n,z rlnc ws,wd wd = rotate left (no carry) ws 1 1 n,z 65 rrc rrc f f = rotate right through carry f 1 1 c,n,z rrc f,wreg wreg = rotate right through carry f 1 1 c,n,z rrc ws,wd wd = rotate right through carry ws 1 1 c,n,z table 21-2: instruction set overview (continued) base instr # assembly mnemonic assembly syntax description # of words # of cycles status flags affected
dspic30f6011/6012/6013/6014 ds70117f-page 168 ? 2006 microchip technology inc. 66 rrnc rrnc f f = rotate right (no carry) f 1 1 n,z rrnc f,wreg wreg = rotate right (no carry) f 1 1 n,z rrnc ws,wd wd = rotate right (no carry) ws 1 1 n,z 67 sac sac acc,#slit4,wdo store accumulator 1 1 none sac.r acc,#slit4,wdo store rounded accumulator 1 1 none 68 se se ws,wnd wnd = sign-extended ws 1 1 c,n,z 69 setm setm f f = 0xffff 1 1 none setm wreg wreg = 0xffff 1 1 none setm ws ws = 0xffff 1 1 none 70 sftac sftac acc,wn arithmetic shift accumulator by (wn) 1 1 oa,ob,oab, sa,sb,sab sftac acc,#slit6 arithmetic shift accumulator by slit6 1 1 oa,ob,oab, sa,sb,sab 71 sl sl f f = left shift f 1 1 c,n,ov,z sl f,wreg wreg = left shift f 1 1 c,n,ov,z sl ws,wd wd = left shift ws 1 1 c,n,ov,z sl wb,wns,wnd wnd = left shift wb by wns 1 1 n,z sl wb,#lit5,wnd wnd = left shift wb by lit5 1 1 n,z 72 sub sub acc subtract accumulators 1 1 oa,ob,oab, sa,sb,sab sub f f = f - wreg 1 1 c,dc,n,ov,z sub f,wreg wreg = f - wreg 1 1 c,dc,n,ov,z sub #lit10,wn wn = wn - lit10 1 1 c,dc,n,ov,z sub wb,ws,wd wd = wb - ws 1 1 c,dc,n,ov,z sub wb,#lit5,wd wd = wb - lit5 1 1 c,dc,n,ov,z 73 subb subb f f = f - wreg - (c ) 1 1 c,dc,n,ov,z subb f,wreg wreg = f - wreg - (c ) 1 1 c,dc,n,ov,z subb #lit10,wn wn = wn - lit10 - (c ) 1 1 c,dc,n,ov,z subb wb,ws,wd wd = wb - ws - (c ) 1 1 c,dc,n,ov,z subb wb,#lit5,wd wd = wb - lit5 - (c ) 1 1 c,dc,n,ov,z 74 subr subr f f = wreg - f 1 1 c,dc,n,ov,z subr f,wreg wreg = wreg - f 1 1 c,dc,n,ov,z subr wb,ws,wd wd = ws - wb 1 1 c,dc,n,ov,z subr wb,#lit5,wd wd = lit5 - wb 1 1 c,dc,n,ov,z 75 subbr subbr f f = wreg - f - (c ) 1 1 c,dc,n,ov,z subbr f,wreg wreg = wreg -f - (c ) 1 1 c,dc,n,ov,z subbr wb,ws,wd wd = ws - wb - (c ) 1 1 c,dc,n,ov,z subbr wb,#lit5,wd wd = lit5 - wb - (c ) 1 1 c,dc,n,ov,z 76 swap swap.b wn wn = nibble swap wn 1 1 none swap wn wn = byte swap wn 1 1 none 77 tblrdh tblrdh ws,wd read prog<23:16> to wd<7:0> 1 2 none 78 tblrdl tblrdl ws,wd read prog<15:0> to wd 1 2 none 79 tblwth tblwth ws,wd write ws<7:0> to prog<23:16> 1 2 none 80 tblwtl tblwtl ws,wd write ws to prog<15:0> 1 2 none 81 ulnk ulnk unlink frame pointer 1 1 none 82 xor xor f f = f .xor. wreg 1 1 n,z xor f,wreg wreg = f .xor. wreg 1 1 n,z xor #lit10,wn wd = lit10 .xor. wd 1 1 n,z xor wb,ws,wd wd = wb .xor. ws 1 1 n,z xor wb,#lit5,wd wd = wb .xor. lit5 1 1 n,z 83 ze ze ws,wnd wnd = zero-extend ws 1 1 c,z,n table 21-2: instruction set overview (continued) base instr # assembly mnemonic assembly syntax description # of words # of cycles status flags affected
? 2006 microchip technology inc. ds70117f-page 169 dspic30f6011/6012/6013/6014 22.0 development support the pic ? microcontrollers are supported with a full range of hardware and software development tools: ? integrated development environment - mplab ? ide software ? assemblers/compilers/linkers - mpasm tm assembler - mplab c18 and mplab c30 c compilers -mplink tm object linker/ mplib tm object librarian - mplab asm30 assembler/linker/library ? simulators - mplab sim software simulator ?emulators - mplab ice 2000 in-circuit emulator - mplab real ice? in-circuit emulator ? in-circuit debugger - mplab icd 2 ? device programmers - picstart ? plus development programmer - mplab pm3 device programmer - pickit? 2 development programmer ? low-cost demonstration and development boards and evaluation kits 22.1 mplab integrated development environment software the mplab ide software brings an ease of software development previously unseen in the 8/16-bit micro- controller market. the mplab ide is a windows ? operating system-based application that contains: ? a single graphical interface to all debugging tools - simulator - programmer (sold separately) - emulator (sold separately) - in-circuit debugger (sold separately) ? a full-featured editor with color-coded context ? a multiple project manager ? customizable data windows with direct edit of contents ? high-level source code debugging ? visual device initializer for easy register initialization ? mouse over variable inspection ? drag and drop variables from source to watch windows ? extensive on-line help ? integration of select third party tools, such as hi-tech software c compilers and iar c compilers the mplab ide allows you to: ? edit your source files (either assembly or c) ? one touch assemble (or compile) and download to pic mcu emulator and simulator tools (automatically updates all project information) ? debug using: - source files (assembly or c) - mixed assembly and c - machine code mplab ide supports multiple debugging tools in a single development paradigm, from the cost-effective simulators, through low-cost in-circuit debuggers, to full-featured emulators. this eliminates the learning curve when upgrading to tools with increased flexibility and power.
dspic30f6011/6012/6013/6014 ds70117f-page 170 ? 2006 microchip technology inc. 22.2 mpasm assembler the mpasm assembler is a full-featured, universal macro assembler for all pic mcus. the mpasm assembler generates relocatable object files for the mplink object linker, intel ? standard hex files, map files to detail memory usage and symbol reference, absolute lst files that contain source lines and generated machine code and coff files for debugging. the mpasm assembler features include: ? integration into mplab ide projects ? user-defined macros to streamline assembly code ? conditional assembly for multi-purpose source files ? directives that allow complete control over the assembly process 22.3 mplab c18 and mplab c30 c compilers the mplab c18 and mplab c30 code development systems are complete ansi c compilers for microchip?s pic18 family of microcontrollers and the dspic30, dspic33 and pic24 family of digital signal controllers. these compilers provide powerful integra- tion capabilities, superior code optimization and ease of use not found with other compilers. for easy source level debugging, the compilers provide symbol information that is optimized to the mplab ide debugger. 22.4 mplink object linker/ mplib object librarian the mplink object linker combines relocatable objects created by the mpasm assembler and the mplab c18 c compiler. it can link relocatable objects from precompiled libraries, using directives from a linker script. the mplib object librarian manages the creation and modification of library files of precompiled code. when a routine from a library is called from a source file, only the modules that contain that routine will be linked in with the application. this allows large libraries to be used efficiently in many different applications. the object linker/library features include: ? efficient linking of single libraries instead of many smaller files ? enhanced code maintainability by grouping related modules together ? flexible creation of libraries with easy module listing, replacement, deletion and extraction 22.5 mplab asm30 assembler, linker and librarian mplab asm30 assembler produces relocatable machine code from symbolic assembly language for dspic30f devices. mplab c30 c compiler uses the assembler to produce its object file. the assembler generates relocatable object files that can then be archived or linked with other relocatable object files and archives to create an executable file. notable features of the assembler include: ? support for the entire dspic30f instruction set ? support for fixed-point and floating-point data ? command line interface ? rich directive set ? flexible macro language ? mplab ide compatibility 22.6 mplab sim software simulator the mplab sim software simulator allows code development in a pc-hosted environment by simulat- ing the pic mcus and dspic ? dscs on an instruction level. on any given instruction, the data areas can be examined or modified and stimuli can be applied from a comprehensive stimulus controller. registers can be logged to files for further run-time analysis. the trace buffer and logic analyzer display extend the power of the simulator to record and track program execution, actions on i/o, most peripherals and internal registers. the mplab sim software simulator fully supports symbolic debugging using the mplab c18 and mplab c30 c compilers, and the mpasm and mplab asm30 assemblers. the software simulator offers the flexibility to develop and debug code outside of the hardware laboratory environment, making it an excellent, economical software development tool.
? 2006 microchip technology inc. ds70117f-page 171 dspic30f6011/6012/6013/6014 22.7 mplab ice 2000 high-performance in-circuit emulator the mplab ice 2000 in-circuit emulator is intended to provide the product development engineer with a complete microcontroller design tool set for pic microcontrollers. software control of the mplab ice 2000 in-circuit emulator is advanced by the mplab integrated development environment, which allows editing, building, downloading and source debugging from a single environment. the mplab ice 2000 is a full-featured emulator system with enhanced trace, trigger and data monitor- ing features. interchangeable processor modules allow the system to be easily reconfigured for emulation of different processors. the architecture of the mplab ice 2000 in-circuit emulator allows expansion to support new pic microcontrollers. the mplab ice 2000 in-circuit emulator system has been designed as a real-time emulation system with advanced features that are typically found on more expensive development tools. the pc platform and microsoft ? windows ? 32-bit operating system were chosen to best make these features available in a simple, unified application. 22.8 mplab real ice in-circuit emulator system mplab real ice in-circuit emulator system is microchip?s next generation high-speed emulator for microchip flash dsc ? and mcu devices. it debugs and programs pic ? and dspic ? flash microcontrollers with the easy-to-use, powerful graphical user interface of the mplab integrated development environment (ide), included with each kit. the mplab real ice probe is connected to the design engineer?s pc using a high-speed usb 2.0 interface and is connected to the target with either a connector compatible with the popular mplab icd 2 system (rj11) or with the new high speed, noise tolerant, low- voltage differential signal (lvds) interconnection (cat5). mplab real ice is field upgradeable through future firmware downloads in mplab ide. in upcoming releases of mplab ide, new devices will be supported, and new features will be added, such as software break- points and assembly code trace. mplab real ice offers significant advantages over competitive emulators including low-cost, full-speed emulation, real-time variable watches, trace analysis, complex breakpoints, a ruggedized probe interface and long (up to three meters) interconnection cables. 22.9 mplab icd 2 in-circuit debugger microchip?s in-circuit debugger, mplab icd 2, is a powerful, low-cost, run-time development tool, connecting to the host pc via an rs-232 or high-speed usb interface. this tool is based on the flash pic mcus and can be used to develop for these and other pic mcus and dspic dscs. the mplab icd 2 utilizes the in-circuit debugging capability built into the flash devices. this feature, along with microchip?s in-circuit serial programming tm (icsp tm ) protocol, offers cost- effective, in-circuit flash debugging from the graphical user interface of the mplab integrated development environment. this enables a designer to develop and debug source code by setting breakpoints, single step- ping and watching variables, and cpu status and peripheral registers. running at full speed enables testing hardware and applications in real time. mplab icd 2 also serves as a development programmer for selected pic devices. 22.10 mplab pm3 device programmer the mplab pm3 device programmer is a universal, ce compliant device programmer with programmable voltage verification at v ddmin and v ddmax for maximum reliability. it features a large lcd display (128 x 64) for menus and error messages and a modu- lar, detachable socket assembly to support various package types. the icsp? cable assembly is included as a standard item. in stand-alone mode, the mplab pm3 device programmer can read, verify and program pic devices without a pc connection. it can also set code protection in this mode. the mplab pm3 connects to the host pc via an rs-232 or usb cable. the mplab pm3 has high-speed communications and optimized algorithms for quick programming of large memory devices and incorporates an sd/mmc card for file storage and secure data applications.
dspic30f6011/6012/6013/6014 ds70117f-page 172 ? 2006 microchip technology inc. 22.11 picstart plus development programmer the picstart plus development programmer is an easy-to-use, low-cost, prototype programmer. it connects to the pc via a com (rs-232) port. mplab integrated development environment software makes using the programmer simple and efficient. the picstart plus development programmer supports most pic devices in dip packages up to 40 pins. larger pin count devices, such as the pic16c92x and pic17c76x, may be supported with an adapter socket. the picstart plus development programmer is ce compliant. 22.12 pickit 2 development programmer the pickit? 2 development programmer is a low-cost programmer and selected flash device debugger with an easy-to-use interface for programming many of microchip?s baseline, mid-range and pic18f families of flash memory microcontrollers. the pickit 2 starter kit includes a prototyping development board, twelve sequential lessons, software and hi-tech?s picc? lite c compiler, and is designed to help get up to speed quickly using pic ? microcontrollers. the kit provides everything needed to program, evaluate and develop applications using microchip?s powerful, mid-range flash memory family of microcontrollers. 22.13 demonstration, development and evaluation boards a wide variety of demonstration, development and evaluation boards for various pic mcus and dspic dscs allows quick application development on fully func- tional systems. most boards include prototyping areas for adding custom circuitry and provide application firmware and source code for examination and modification. the boards support a variety of features, including leds, temperature sensors, switches, speakers, rs-232 interfaces, lcd displays, potentiometers and additional eeprom memory. the demonstration and development boards can be used in teaching environments, for prototyping custom circuits and for learning about various microcontroller applications. in addition to the picdem? and dspicdem? demon- stration/development board series of circuits, microchip has a line of evaluation kits and demonstration software for analog filter design, k ee l oq ? security ics, can, irda ? , powersmart ? battery management, seeval ? evaluation system, sigma-delta adc, flow rate sensing, plus many more. check the microchip web page (www.microchip.com) and the latest ?product selector guide? (ds00148) for the complete list of demonstration, development and evaluation kits.
? 2006 microchip technology inc. ds70117f-page 173 dspic30f6011/6012/6013/6014 23.0 electrical characteristics this section provides an overview of dspic30f electrical ch aracteristics. additional information will be provided in future revisions of this document as it becomes available. for detailed information about the dspic30f architecture and core, refer to ? dspic30f family reference manual? (ds70046). absolute maximum ratings for the dspic30f family are listed below. exposure to these maximum rating conditions for extended periods may affect device reliability. functional operation of the device at these or any other conditions above the parameters indicated in the operation listings of this specification is not implied. absolute maximum ratings (?) ambient temperature under bias................................................................................................. ............-40c to +125c storage temperature ............................................................................................................ .................. -65c to +150c voltage on any pin with respect to v ss (except v dd and mclr ) (note 1) ..................................... -0.3v to (v dd + 0.3v) voltage on v dd with respect to v ss ......................................................................................................... -0.3v to +5.5v voltage on mclr with respect to v ss ....................................................................................................... 0v to +13.25v maximum current out of v ss pin ........................................................................................................................... 300 ma maximum current into v dd pin (note 2) ................................................................................................................250 ma input clamp current, i ik (v i < 0 or v i > v dd ) .......................................................................................................... 20 ma output clamp current, i ok (v o < 0 or v o > v dd ) ...................................................................................................20 ma maximum output current sunk by any i/o pin..................................................................................... .....................25 ma maximum output current sourced by any i/o pin .................................................................................. ..................25 ma maximum current sunk by all ports .............................................................................................. .........................200 ma maximum current sourced by all ports (note 2) ....................................................................................................200 ma note 1: voltage spikes below v ss at the mclr /v pp pin, inducing currents greater than 80 ma, may cause latchup. thus, a series resistor of 50-100 should be used when applying a ?low? level to the mclr /v pp pin, rather than pulling this pin directly to v ss . 2: maximum allowable current is a function of device maximum power dissipation. see table 23-2 for p dmax . 23.1 dc characteristics ? notice: stresses above those listed under ?absolute maximum ratings? may cause permanent damage to the device. this is a stress rating only and functional operation of the device at those or any other conditions above those indicated in the operation listings of this specification is not implied. exposure to maximum rating conditions for extended periods may affect device reliability. note: all peripheral electrical characteristics are specified. for exact peripherals available on specific devices, please refer the family cross reference table. table 23-1: operating mips vs. voltage v dd range temp range max mips dspic30f601x-30i dspic30f601x-20i dspic30f601x-20e 4.75-5.5v -40c to 85c 30 20 ? 4.75-5.5v -40c to 125c ? ? 20 3.0-3.6v -40c to 85c 15 10 ? 3.0-3.6v -40c to 125c ? ? 10 2.5-3.0v -40c to 85c 7.5 7.5 ?
dspic30f6011/6012/6013/6014 ds70117f-page 174 ? 2006 microchip technology inc. table 23-2: thermal operating conditions rating symbol min typ max unit dspic30f601x-30i operating junction temperature range t j -40 +125 c operating ambient temperature range t a -40 +85 c dspic30f601x-20i operating junction temperature range t j -40 +150 c operating ambient temperature range t a -40 +85 c dspic30f601x-20e operating junction temperature range t j -40 +150 c operating ambient temperature range t a -40 +125 c power dissipation: internal chip power dissipation: p d p int + p i / o w i/o pin power dissipation: maximum allowed power dissipation p dmax (t j - t a ) / ja w table 23-3: thermal packaging characteristics characteristic symbol typ max unit notes package thermal resistance, 80-pin tqfp (14x14x1mm) ja 50 c/w 1 package thermal resistance, 64-pin tqfp (14x14x1mm) ja 50 c/w 1 note 1: junction to ambient thermal resistance, theta-ja ( ja ) numbers are achieved by package simulations. table 23-4: dc temperature and voltage specifications dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ (1) max units conditions operating voltage (2) dc10 v dd supply voltage 2.5 ? 5.5 v industrial temperature dc11 v dd supply voltage 3.0 ? 5.5 v extended temperature dc12 v dr ram data retention voltage (3) ?1.5?v dc16 v por v dd start voltage to ensure internal power-on reset signal ?v ss ?v dc17 s vdd v dd rise rate to ensure internal power-on reset signal 0.05 v/ms 0-5v in 0.1 sec 0-3v in 60 ms note 1: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: these parameters are characterized but not tested in manufacturing. 3: this is the limit to which v dd can be lowered without losing ram data. p int v dd i dd i oh ? () = p i / o v dd v oh ? {} i oh () v ol i ol () + =
? 2006 microchip technology inc. ds70117f-page 175 dspic30f6011/6012/6013/6014 table 23-5: dc characteristics: operating current (i dd ) dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended parameter no. typical (1) max units conditions operating current (i dd ) (2) dc31a 6.8 10 ma 25c 3.3v 0.128 mips lprc (512 khz) dc31b 6.3 10 ma 85c dc31c 6.1 10 ma 125c dc31e 16 22 ma 25c 5v dc31f 15 22 ma 85c dc31g 15 22 ma 125c dc30a 13 19 ma 25c 3.3v (1.8 mips) frc (7.37 mhz) dc30b 13 19 ma 85c dc30c 13 19 ma 125c dc30e 27 39 ma 25c 5v dc30f 26 39 ma 85c dc30g 25 39 ma 125c dc23a 27 41 ma 25c 3.3v 4 mips dc23b 27 41 ma 85c dc23c 27 41 ma 125c dc23e 41 60 ma 25c 5v dc23f 40 60 ma 85c dc23g 40 60 ma 125c dc24a 46 71 ma 25c 3.3v 10 mips dc24b 46 71 ma 85c dc24c 47 71 ma 125c dc24e 79 120 ma 25c 5v dc24f 78 120 ma 85c dc24g 78 120 ma 125c dc27a 83 120 ma 25c 3.3v 20 mips dc27b 83 120 ma 85c dc27d 138 190 ma 25c 5v dc27e 137 190 ma 85c dc27f 136 190 ma 125c dc29a 194 255 ma 25c 5v 30 mips dc29b 192 255 ma 85c note 1: data in ?typical? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: the supply current is mainly a function of the operating voltage and frequency. other factors such as i/o pin loading and switching rate, oscillator type, internal code execution pattern and temperature also have an impact on the current consumption. the test conditions for all i dd measurements are as follows: osc1 driven with external square wave from rail to rail. all i/o pins are configured as inputs and pulled to v dd . mclr = v dd , wdt, fscm, lvd and bor are disabled. cpu, sram, program memory and data memory are operational. no peripheral modules are operating.
dspic30f6011/6012/6013/6014 ds70117f-page 176 ? 2006 microchip technology inc. table 23-6: dc characteristics: idle current (i idle ) dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended parameter no. typical (1) max units conditions operating current (i idle ) (2) dc51a 6.3 9 ma 25c 3.3v 0.128 mips lprc (512 khz) dc51b 5.9 9 ma 85c dc51c 5.7 9 ma 125c dc51e 16 21 ma 25c 5v dc51f 15 21 ma 85c dc51g 15 21 ma 125c dc50a 10 15 ma 25c 3.3v (1.8 mips) frc (7.37 mhz) dc50b 10 15 ma 85c dc50c 10 15 ma 125c dc50e 21 30 ma 25c 5v dc50f 20 30 ma 85c dc50g 19 30 ma 125c dc43a 15 23 ma 25c 3.3v 4 mips dc43b 15 23 ma 85c dc43c 15 23 ma 125c dc43e 30 45 ma 25c 5v dc43f 29 45 ma 85c dc43g 29 45 ma 125c dc44a 28 42 ma 25c 3.3v 10 mips dc44b 28 42 ma 85c dc44c 28 42 ma 125c dc44e 50 70 ma 25c 5v dc44f 49 70 ma 85c dc44g 49 70 ma 125c dc47a 49 70 ma 25c 3.3v 20 mips dc47b 50 70 ma 85c dc47d 84 110 ma 25c 5v dc47e 84 110 ma 85c dc47f 83 110 ma 125c dc49a 117 145 ma 25c 5v 30 mips dc49b 117 145 ma 85c note 1: data in ?typical? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: base i idle current is measured with core off, clock on and all modules turned off.
? 2006 microchip technology inc. ds70117f-page 177 dspic30f6011/6012/6013/6014 table 23-7: dc characteristics: power-down current (i pd ) dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended parameter no. typical (1) max units conditions power down current (i pd ) dc60a 0.3 ? a 25c 3.3v base power down current (2) dc60b 2 60 a 85c dc60c 23 120 a 125c dc60e 0.5 ? a 25c 5v dc60f 3 110 a 85c dc60g 32 180 a 125c dc61a 10 20 a 25c 3.3v watchdog timer current: i wdt (3) dc61b 10 20 a 85c dc61c 10 20 a 125c dc61e 18 30 a 25c 5v dc61f 17 30 a 85c dc61g 17 30 a 125c dc62a 4 10 a 25c 3.3v timer 1 w/32 khz crystal: i ti 32 (3) dc62b 5 10 a 85c dc62c 4 10 a 125c dc62e 4 15 a 25c 5v dc62f 6 15 a 85c dc62g 5 15 a 125c dc63a 30 55 a 25c 3.3v bor on: i bor (3) dc63b 32 55 a 85c dc63c 34 55 a 125c dc63e 34 60 a 25c 5v dc63f 37 60 a 85c dc63g 38 60 a 125c dc66a 18 35 a 25c 3.3v low-voltage detect: i lvd (3) dc66b 20 35 a 85c dc66c 21 35 a 125c dc66e 22 40 a 25c 5v dc66f 23 40 a 85c dc66g 24 40 a 125c note 1: data in the typical column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: base i pd is measured with all peripherals and clocks shut down. all i/os are configured as inputs and pulled high. lvd, bor, wdt, etc. are all switched off. 3: the current is the additional current consumed when the module is enabled. this current should be added to the base i pd current.
dspic30f6011/6012/6013/6014 ds70117f-page 178 ? 2006 microchip technology inc. table 23-8: dc characteristics: i/o pin input specifications dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ (1) max units conditions v il input low voltage (2) di10 i/o pins: with schmitt trigger buffer v ss ?0.2v dd v di15 mclr v ss ?0.2v dd v di16 osc1 (in xt, hs and lp modes) v ss ?0.2v dd v di17 osc1 (in rc mode) (3) v ss ?0.3v dd v di18 sda, scl v ss ?0.3v dd v smbus disabled di19 sda, scl v ss ?0.2v dd v smbus enabled v ih input high voltage (2) di20 i/o pins: with schmitt trigger buffer 0.8 v dd ?v dd v di25 mclr 0.8 v dd ?v dd v di26 osc1 (in xt, hs and lp modes) 0.7 v dd ?v dd v di27 osc1 (in rc mode) (3) 0.9 v dd ?v dd v di28 sda, scl 0.7 v dd ?v dd v smbus disabled di29 sda, scl 0.8 v dd ?v dd v smbus enabled i cnpu cn xx pull-up current (2) di30 50 250 400 av dd = 5v, v pin = v ss i il input leakage current (2)(4)(5) di50 i/o ports ? 0.01 1 av ss v pin v dd , pin at high-impedance di51 analog input pins ? 0.50 ? av ss v pin v dd , pin at high-impedance di55 mclr ?0.055 av ss v pin v dd di56 osc1 ? 0.05 5 av ss v pin v dd , xt, hs and lp osc mode note 1: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: these parameters are characterized but not tested in manufacturing. 3: in rc oscillator configuration, the osc1/clkl pin is a schmitt trigger input. it is not recommended that the dspic30f device be driven with an external clock while in rc mode. 4: the leakage current on the mclr pin is strongly dependent on the applied voltage level. the specified levels represent normal operating conditions. higher leakage current may be measured at different input voltages. 5: negative current is defined as current sourced by the pin.
? 2006 microchip technology inc. ds70117f-page 179 dspic30f6011/6012/6013/6014 figure 23-1: low-voltage detect characteristics table 23-9: dc characteristics: i/o pin output specifications dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ (1) max units conditions v ol output low voltage (2) do10 i/o ports ? ? 0.6 v i ol = 8.5 ma, v dd = 5v ??tbdvi ol = 2.0 ma, v dd = 3v do16 osc2/clko ? ? 0.6 v i ol = 1.6 ma, v dd = 5v (rc or ec osc mode) ? ? tbd v i ol = 2.0 ma, v dd = 3v v oh output high voltage (2) do20 i/o ports v dd ? 0.7 ? ? v i oh = -3.0 ma, v dd = 5v tbd ? ? v i oh = -2.0 ma, v dd = 3v do26 osc2/clko v dd ? 0.7 ? ? v i oh = -1.3 ma, v dd = 5v (rc or ec osc mode) tbd ? ? v i oh = -2.0 ma, v dd = 3v capacitive loading specs on output pins (2) do50 c osc 2 osc2/sosc2 pin ? ? 15 pf in xtl, xt, hs and lp modes when external clock is used to drive osc1. do56 c io all i/o pins and osc2 ? ? 50 pf rc or ec osc mode do58 c b scl, sda ? ? 400 pf in i 2 c mode note 1: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: these parameters are characterized but not tested in manufacturing. lv10 lvdif v dd (lvdif set by hardware)
dspic30f6011/6012/6013/6014 ds70117f-page 180 ? 2006 microchip technology inc. figure 23-2: brown-out reset characteristics table 23-10: electrical characteristics: lvdl dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ max units conditions lv10 v plvd lvdl voltage on v dd transition high to low lvdl = 0000 (2) ???v lvdl = 0001 (2) ???v lvdl = 0010 (2) ???v lvdl = 0011 (2) ???v lvdl = 0100 2.50 ? 2.65 v lvdl = 0101 2.70 ? 2.86 v lvdl = 0110 2.80 ? 2.97 v lvdl = 0111 3.00 ? 3.18 v lvdl = 1000 3.30 ? 3.50 v lvdl = 1001 3.50 ? 3.71 v lvdl = 1010 3.60 ? 3.82 v lvdl = 1011 3.80 ? 4.03 v lvdl = 1100 4.00 ? 4.24 v lvdl = 1101 4.20 ? 4.45 v lvdl = 1110 4.50 ? 4.77 v lv15 v lvdin external lvd input pin threshold voltage lvdl = 1111 ???v note 1: these parameters are characterized but not tested in manufacturing. 2: these values not in usable operating range. bo10 reset (due to bor) v dd (device in brown-out reset) (device not in brown-out reset) power up time-out bo15
? 2006 microchip technology inc. ds70117f-page 181 dspic30f6011/6012/6013/6014 table 23-12: dc characteristics: program and eeprom table 23-11: electrical characteristics: bor dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ (1) max units conditions bo10 v bor bor voltage (2) on v dd transition high to low borv = 11 (3) ? ? ? v not in operating range borv = 10 2.6 ? 2.71 v borv = 01 4.1 ? 4.4 v borv = 00 4.58 ? 4.73 v bo15 v bhys ?5?mv note 1: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: these parameters are characterized but not tested in manufacturing. 3: ? 11 ? values not in usable operating range. dc characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ (1) max units conditions data eeprom memory (2) d120 e d byte endurance 100k 1m ? e/w -40 c t a +85c d121 v drw v dd for read/write v min ? 5.5 v using eecon to read/write v min = minimum operating voltage d122 t dew erase/write cycle time ? 2 ? ms d123 t retd characteristic retention 40 100 ? year provided no other specifications are violated d124 i dew i dd during programming ? 10 30 ma row erase program flash memory (2) d130 e p cell endurance 10k 100k ? e/w -40 c t a +85c d131 v pr v dd for read v min ?5.5vv min = minimum operating voltage d132 v eb v dd for bulk erase 4.5 ? 5.5 v d133 v pew v dd for erase/write 3.0 ? 5.5 v d134 t pew erase/write cycle time ? 2 ? ms d135 t retd characteristic retention 40 100 ? year provided no other specifications are violated d136 t eb icsp block erase time ? 4 ? ms d137 i pew i dd during programming ? 10 30 ma row erase d138 i eb i dd during programming ? 10 30 ma bulk erase note 1: data in ?typ? column is at 5v, 25c unless otherwise stated. 2: these parameters are characterized but not tested in manufacturing.
dspic30f6011/6012/6013/6014 ds70117f-page 182 ? 2006 microchip technology inc. 23.2 ac characteristics and timing parameters the information contained in this section defines dspic30f ac characteristics and timing parameters. figure 23-3: load conditions for de vice timing specifications figure 23-4: external clock timing table 23-13: temperature and voltage sp ecifications ? ac ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended operating voltage v dd range as described in dc spec section 23.0 ?electrical characteristics? . v dd /2 c l r l pin pin v ss v ss c l r l = 464 c l = 50 pf for all pins except osc2 5 pf for osc2 output load condition 1 ? for all pins except osc2 load condition 2 ? for osc2 osc1 clko q4 q1 q2 q3 q4 q1 os20 os25 os30 os30 os40 os41 os31 os31
? 2006 microchip technology inc. ds70117f-page 183 dspic30f6011/6012/6013/6014 table 23-14: external clock timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ (1) max units conditions os10 f osc external clki frequency (2) (external clocks allowed only in ec mode) dc 4 4 4 ? ? ? ? 40 10 10 7.5 mhz mhz mhz mhz ec ec with 4x pll ec with 8x pll ec with 16x pll oscillator frequency (2) dc 0.4 4 4 4 4 10 31 ? ? ? ? ? ? ? ? ? ? 7.37 512 4 4 10 10 10 7.5 25 33 ? ? mhz mhz mhz mhz mhz mhz mhz khz mhz khz rc xtl xt xt with 4x pll xt with 8x pll xt with 16x pll hs lp frc internal lprc internal os20 t osc t osc = 1/f osc ? ? ? ? see parameter os10 for f osc value os25 t cy instruction cycle time (2)(3) 33 ? dc ns see table 23-17 os30 tosl, to s h external clock (2) in (osc1) high or low time .45 x t osc ??nsec os31 tosr, to s f external clock (2) in (osc1) rise or fall time ??20nsec os40 tckr clko rise time (2)(4) ?610ns os41 tckf clko fall time (2)(4) ?610ns note 1: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 2: these parameters are characterized but not tested in manufacturing. 3: instruction cycle period (t cy ) equals four times the input oscillator time base period. all specified values are based on characterization data for that particular oscillator type under standard operating conditions with the device executing code. exceeding these specified limits may result in an unstable oscillator operation and/or higher than expected current consumpt ion. all devices are tested to operate at ?min.? values with an external clock applied to the osc1/clki pin. when an external clock input is used, the ?max.? cycle time limit is ?dc? (no clock) for all devices. 4: measurements are taken in ec or erc modes. the clko signal is measured on the osc2 pin. clko is low for the q1-q2 period (1/2 t cy ) and high for the q3-q4 period (1/2 t cy ).
dspic30f6011/6012/6013/6014 ds70117f-page 184 ? 2006 microchip technology inc. table 23-15: pll clock ti ming specifications (v dd = 2.5 to 5.5 v) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions os50 f plli pll input frequency range (2) 4 4 4 4 4 4 ? ? ? ? ? ? 10 10 7.5 (3) 10 10 7.5 (3) mhz mhz mhz mhz mhz mhz ec with 4x pll ec with 8x pll ec with 16x pll xt with 4x pll xt with 8x pll xt with 16x pll os51 f sys on-chip pll output (2) 16 ? 120 mhz ec, xt modes with pll os52 t loc pll start-up time (lock time) ? 20 50 s note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: limited by device operating frequency range. table 23-16: pll jitter ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40c t a +125c for extended param no. characteristic min typ (1) max units conditions os61 x4 pll ? 0.251 0.413 % -40c t a +85c v dd = 3.0 to 3.6v ? 0.251 0.413 % -40c t a +125c v dd = 3.0 to 3.6v ? 0.256 0.47 % -40c t a +85c v dd = 4.5 to 5.5v ? 0.256 0.47 % -40c t a +125c v dd = 4.5 to 5.5v x8 pll ? 0.355 0.584 % -40c t a +85c v dd = 3.0 to 3.6v ? 0.355 0.584 % -40c t a +125c v dd = 3.0 to 3.6v ? 0.362 0.664 % -40c t a +85c v dd = 4.5 to 5.5v ? 0.362 0.664 % -40c t a +125c v dd = 4.5 to 5.5v x16 pll ? 0.67 0.92 % -40c t a +85c v dd = 3.0 to 3.6v ? 0.632 0.956 % -40c t a +85c v dd = 4.5 to 5.5v ? 0.632 0.956 % -40c t a +125c v dd = 4.5 to 5.5v note 1: these parameters are characterized but not tested in manufacturing. table 23-17: internal clock timing examples clock oscillator mode f osc (mhz) (1) t cy ( sec) (2) mips (3) w/o pll mips (3) w/pll x4 mips (3) w/pll x8 mips (3) w/pll x16 ec 0.200 20.0 0.05 ? ? ? 4 1.0 1.0 4.0 8.0 16.0 10 0.4 2.5 10.0 20.0 ? 25 0.16 6.25 ? ? ? xt 4 1.0 1.0 4.0 8.0 16.0 10 0.4 2.5 10.0 20.0 ?
? 2006 microchip technology inc. ds70117f-page 185 dspic30f6011/6012/6013/6014 note 1: assumption: oscillator postscaler is divide by 1. 2: instruction execution cycle time: t cy = 1 / mips. 3: instruction execution frequency: mips = (f osc * pllx)/4 [since there are 4 q clocks per instruction cycle]. table 23-17: internal clock timing examples table 23-18: ac characteristics: internal rc accuracy (2) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40c t a +125c for extended param no. characteristic min typ max units conditions internal frc jitter @ frc freq. = 7.37 mhz (1) os62 frc ? + 0.04 + 0.16 % -40c t a +85c v dd = 3.0-3.6v ?+ 0.07 + 0.23 % -40c t a +125c v dd = 4.5-5.5v internal frc accuracy @ frc freq. = 7.37 mhz (1) os63 frc ? ? + 1.50 % -40c t a +125c v dd = 3.0-5.5v internal frc drift @ frc freq. = 7.37 mhz (1) os64 -0.7 ? 0.5 % -40c t a +85c v dd = 3.0-3.6v -0.7 ? 0.7 % -40c t a +125c v dd = 3.0-3.6v -0.7 ? 0.5 % -40c t a +85c v dd = 4.5-5.5v -0.7 ? 0.7 % -40c t a +125c v dd = 4.5-5.5v note 1: frequency calibrated at 7.372 mhz 2%, 25c and 5v. tun <3:0> bits can be used to compensate for temperature drift. 2: overall frc variation can be calculated by adding the absolute values of jitter, accuracy and drift percent- ages. table 23-19: internal rc accuracy ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. characteristic min typ max units conditions lprc @ freq. = 512 khz (1) os65 -35 ? +35 % ? note 1: change of lprc frequency as v dd changes.
dspic30f6011/6012/6013/6014 ds70117f-page 186 ? 2006 microchip technology inc. figure 23-5: clko and i/o timing characteristics note: refer to figure 23-3 for load conditions. i/o pin (input) i/o pin (output) di35 old value new value di40 do31 do32 table 23-20: clko and i/o timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1)(2)(3) min typ (4) max units conditions do31 t io r port output rise time ? 7 20 ns ? do32 t io f port output fall time ? 7 20 ns ? di35 t inp intx pin high or low time (output) 20 ? ? ns ? di40 t rbp cnx high or low time (input) 2 t cy ??ns ? note 1: these parameters are asynchronous events not related to any internal clock edges 2: measurements are taken in rc mode and ec mode where clko output is 4 x t osc . 3: these parameters are characterized but not tested in manufacturing. 4: data in ?typ? column is at 5v, 25c unless otherwise stated.
? 2006 microchip technology inc. ds70117f-page 187 dspic30f6011/6012/6013/6014 figure 23-6: reset, watchdog timer, oscillator start-up timer and power-up timer timing characteristics table 23-21: reset, watchdog timer, oscillator start-up timer, power-up timer and brown-out reset timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions sy10 tmcl mclr pulse width (low) 2 ? ? s -40c to +85c sy11 t pwrt power-up timer period 3 12 50 4 16 64 6 22 90 ms -40c to +85c user programmable sy12 t por power on reset delay 3 10 30 s -40c to +85c sy13 t ioz i/o high-impedance from mclr low or watchdog timer reset ?0.81.0 s sy20 t wdt 1 watchdog timer time-out period (no prescaler) 1.4 2.1 2.8 ms v dd = 3.3v, -40c to +85c t wdt 2 1.4 2.1 2.8 ms v dd = 5.0v, -40c to +85c note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. 3: refer to figure 23-2 and table 23-11 for bor. v dd mclr internal por pwrt time-out osc time-out internal reset watchdog timer reset sy11 sy10 sy20 sy13 i/o pins sy13 note: refer to figure 23-3 for load conditions. fscm delay sy35 sy30 sy12
dspic30f6011/6012/6013/6014 ds70117f-page 188 ? 2006 microchip technology inc. figure 23-7: band gap start-up time characteristics sy25 t bor brown-out reset pulse width (3) 100 ? ? sv dd v bor (d034) sy30 t ost oscillation start-up timer period ? 1024 t osc ??t osc = osc1 period sy35 t fscm fail-safe clock monitor delay ? 500 900 s -40c to +85c table 23-21: reset, watchdog timer, oscillator start-up timer, power-up timer and brown-out reset timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. 3: refer to figure 23-2 and table 23-11 for bor. v bgap enable band gap band gap 0v (see note) stable note: set lvden bit (rcon<12>) or the boren bit (fborpor<7>). sy40 table 23-22: band gap start-up time requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions sy40 t bgap band gap start-up time ? 40 65 s defined as the time between the instant that the band gap is enabled and the moment that the band gap reference voltage is stable. rcon<13>status bit note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated.
? 2006 microchip technology inc. ds70117f-page 189 dspic30f6011/6012/6013/6014 figure 23-8: type a, b and c timer extern al clock timing characteristics table 23-23: type a timer (timer1) external clock timing requirements (1) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ max units conditions ta10 t tx h txck high time synchronous, no prescaler 0.5 t cy + 20 ? ? ns must also meet parameter ta15 synchronous, with prescaler 10 ? ? ns asynchronous 10 ? ? ns ta11 t tx l txck low time synchronous, no prescaler 0.5 t cy + 20 ? ? ns must also meet parameter ta15 synchronous, with prescaler 10 ? ? ns asynchronous 10 ? ? ns ta15 t tx p txck input period synchronous, no prescaler t cy + 10 ? ? ns synchronous, with prescaler greater of: 20 ns or (t cy + 40)/n ???n = prescale value (1, 8, 64, 256) asynchronous 20 ? ? ns os60 ft1 sosc1/t1ck oscillator input frequency range (oscillator enabled by setting bit tcs (t1con, bit 1)) dc ? 50 khz ta20 t ckextmrl delay from external txck clock edge to timer increment 0.5 t cy 1.5 t cy ? note 1: timer1 is a type a. note: refer to figure 23-3 for load conditions. tx11 tx15 tx10 tx20 tmrx os60 txck
dspic30f6011/6012/6013/6014 ds70117f-page 190 ? 2006 microchip technology inc. table 23-24: type b timer (timer2 and timer4) external clock timing requirements (1) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ max units conditions tb10 ttxh txck high time synchronous, no prescaler 0.5 t cy + 20 ? ? ns must also meet parameter tb15 synchronous, with prescaler 10 ? ? ns tb11 ttxl txck low time synchronous, no prescaler 0.5 t cy + 20 ? ? ns must also meet parameter tb15 synchronous, with prescaler 10 ? ? ns tb15 ttxp txck input period synchronous, no prescaler t cy + 10 ? ? ns n = prescale value (1, 8, 64, 256) synchronous, with prescaler greater of: 20 ns or (t cy + 40)/n tb20 t ckext - mrl delay from external txck clock edge to timer increment 0.5 t cy ? 1.5 t cy ? note 1: timer2 and timer4 are type b. table 23-25: type c timer (timer3 and timer5) external clock timing requirements (1) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min typ max units conditions tc10 ttxh txck high time synchronous 0.5 t cy + 20 ? ? ns must also meet parameter tc15 tc11 ttxl txck low time synchronous 0.5 t cy + 20 ? ? ns must also meet parameter tc15 tc15 ttxp txck input period synchronous, no prescaler t cy + 10 ? ? ns n = prescale value (1, 8, 64, 256) synchronous, with prescaler greater of: 20 ns or (t cy + 40)/n tc20 t ckext - mrl delay from external txck clock edge to timer increment 0.5 t cy ?1.5 t cy ? note 1: timer3 and timer5 are type c.
? 2006 microchip technology inc. ds70117f-page 191 dspic30f6011/6012/6013/6014 figure 23-9: input capture (capx) timing characteristics figure 23-10: output compare module (o cx) timing characteristics table 23-26: input capture timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min max units conditions ic10 tccl icx input low time no prescaler 0.5 t cy + 20 ? ns with prescaler 10 ? ns ic11 tcch icx input high time no prescaler 0.5 t cy + 20 ? ns with prescaler 10 ? ns ic15 tccp icx input period (2 t cy + 40)/n ? ns n = prescale value (1, 4, 16) note 1: these parameters are characterized but not tested in manufacturing. table 23-27: output compare module timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions oc10 tccf ocx output fall time ? ? ? ns see parameter d032 oc11 tccr ocx output rise time ? ? ? ns see parameter d031 note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. ic x ic10 ic11 ic15 note: refer to figure 23-3 for load conditions. ocx oc11 oc10 (output compare note: refer to figure 23-3 for load conditions. or pwm mode)
dspic30f6011/6012/6013/6014 ds70117f-page 192 ? 2006 microchip technology inc. figure 23-11: oc/pwm module ti ming characteristics table 23-28: simple oc/pwm mode timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions oc15 t fd fault input to pwm i/o change ??50ns ? oc20 t flt fault input pulse width 50 ? ? ns ? note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. ocfa/ocfb ocx oc20 oc15
? 2006 microchip technology inc. ds70117f-page 193 dspic30f6011/6012/6013/6014 figure 23-12: dci module (multichannel, i 2 s modes) timing characteristics cofs csck (scke = 0 ) csck (scke = 1 ) csdo csdi cs11 cs10 cs40 cs41 cs21 cs20 cs35 cs21 msb lsb msb in lsb in cs31 high-z high-z 70 cs30 cs51 cs50 cs55 note: refer to figure 23-3 for load conditions. cs20 cs56
dspic30f6011/6012/6013/6014 ds70117f-page 194 ? 2006 microchip technology inc. table 23-29: dci module (multichannel, i 2 s modes) timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions cs10 tc sckl csck input low time (csck pin is an input) t cy /2 + 20 ? ? ns ? csck output low time (3) (csck pin is an output) 30 ? ? ns ? cs11 tc sckh csck input high time (csck pin is an input) t cy /2 + 20 ? ? ns ? csck output high time (3) (csck pin is an output) 30 ? ? ns ? cs20 tc sckf csck output fall time (4) (csck pin is an output) ?1025ns ? cs21 tc sckr csck output rise time (4) (csck pin is an output) ?1025ns ? cs30 tc sdof csdo data output fall time (4) ?1025ns ? cs31 tc sdor csdo data output rise time (4) ?1025ns ? cs35 t dv clock edge to csdo data valid ? ? 10 ns ? cs36 t div clock edge to csdo tri-stated 10 ? 20 ns ? cs40 t csdi setup time of csdi data input to csck edge (csck pin is input or output) 20 ? ? ns ? cs41 t hcsdi hold time of csdi data input to csck edge (csck pin is input or output) 20 ? ? ns ? cs50 tco fsf (1) cofs fall time (cofs pin is output) ?1025ns ? cs51 tco fsr (1) cofs rise time (cofs pin is output) ?1025ns ? cs55 tsco fs setup time of cofs data input to csck edge (cofs pin is input) 20 ? ? ns ? cs56 t hcofs hold time of cofs data input to csck edge (cofs pin is input) 20 ? ? ns ? note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: the minimum clock period for csck is 100 ns. therefore, the clock generated in master mode must not violate this specification. 4: assumes 50 pf load on all dci pins.
? 2006 microchip technology inc. ds70117f-page 195 dspic30f6011/6012/6013/6014 figure 23-13: dci module (ac-link mo de) timing characteristics table 23-30: dci module (ac-link mode) timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1)(2) min typ (3) max units conditions cs60 t bclkl bit_clk low time 36 40.7 45 ns ? cs61 t bclkh bit_clk high time 36 40.7 45 ns ? cs62 t bclk bit_clk period ? 81.4 ? ns bit clock is input cs65 t sacl input setup time to falling edge of bit_clk ?? 10 ns ? cs66 t hacl input hold time from falling edge of bit_clk ?? 10 ns ? cs70 t synclo sync data output low time (1) ?19.5 ? s? cs71 t synchi sync data output high time (1) ?1.3 ? s? cs72 t sync sync data output period (1) ?20.8 ? s? cs75 t racl rise time, sync, sdata_out ?10 25 nsc load = 50 pf, v dd = 5v cs76 t facl fall time, sync, sdata_out ? 10 25 ns c load = 50 pf, v dd = 5v cs77 t racl rise time, sync, sdata_out ?tbdtbd nsc load = 50 pf, v dd = 3v note 1: these parameters are characterized but not tested in manufacturing. 2: these values assume bit_clk frequency is 12.288 mhz. 3: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. sync bit_clk sdo sdi cs61 cs60 cs65 cs66 cs80 cs21 msb in cs75 lsb cs76 (cofs) (csck) lsb msb cs72 cs71 cs70 cs76 cs75 (csdo) (csdi) cs62 cs20
dspic30f6011/6012/6013/6014 ds70117f-page 196 ? 2006 microchip technology inc. figure 23-14: spi module master mode (cke = 0 ) timing characteristics cs78 t facl fall time, sync, sdata_out ? tbd tbd ns c load = 50 pf, v dd = 3v cs80 t ovdacl output valid delay from rising edge of bit_clk ?? 15 ns ? table 23-31: spi master mode (cke = 0 ) timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions sp10 tscl sck x output low time (3) t cy / 2 ? ? ns ? sp11 tsch sck x output high time (3) t cy /2 ? ? ns ? note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: the minimum clock period for sck is 100 ns. therefore, the clock generated in master mode must not violate this specification. 4: assumes 50 pf load on all spi pins. table 23-30: dci module (ac-link mode) timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1)(2) min typ (3) max units conditions note 1: these parameters are characterized but not tested in manufacturing. 2: these values assume bit_clk frequency is 12.288 mhz. 3: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. sckx (ckp = 0 ) sckx (ckp = 1 ) sdox sdix sp11 sp10 sp40 sp41 sp21 sp20 sp35 sp20 sp21 msb lsb bit14 - - - - - -1 msb in lsb in bit14 - - - -1 sp30 sp31 note: refer to figure 23-3 for load conditions.
? 2006 microchip technology inc. ds70117f-page 197 dspic30f6011/6012/6013/6014 figure 23-15: spi module master mode (cke = 1 ) timing characteristics sp20 tscf sck x output fall time (4) ? ? ? ns see parameter d032 sp21 tscr sck x output rise time (4) ? ? ? ns see parameter d031 sp30 tdof sdo x data output fall time (4) ? ? ? ns see parameter d032 sp31 tdor sdo x data output rise time (4) ? ? ? ns see parameter d031 sp35 tsch2dov, tscl2dov sdo x data output valid after sck x edge ? ? 30 ns ? sp40 tdiv2sch, tdiv2scl setup time of sdi x data input to sck x edge 20 ? ? ns ? sp41 tsch2dil, ts c l 2 d i l hold time of sdi x data input to sck x edge 20 ? ? ns ? table 23-31: spi master mode (cke = 0 ) timing requirements (continued) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: the minimum clock period for sck is 100 ns. therefore, the clock generated in master mode must not violate this specification. 4: assumes 50 pf load on all spi pins. sck x (ckp = 0 ) sck x (ckp = 1 ) sdo x sdi x sp36 sp30,sp31 sp35 msb msb in bit14 - - - - - -1 lsb in bit14 - - - -1 lsb note: refer to figure 23-3 for load conditions. sp11 sp10 sp20 sp21 sp21 sp20 sp40 sp41
dspic30f6011/6012/6013/6014 ds70117f-page 198 ? 2006 microchip technology inc. figure 23-16: spi module slave mode (cke = 0 ) timing characteristics table 23-32: spi module master mode (cke = 1 ) timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions sp10 tscl sck x output low time (3) t cy /2 ? ? ns ? sp11 tsch sck x output high time (3) t cy /2 ? ? ns ? sp20 tscf sck x output fall time (4) ? ? ? ns see parameter d032 sp21 tscr sck x output rise time (4) ? ? ? ns see parameter d031 sp30 tdof sdo x data output fall time (4) ? ? ? ns see parameter d032 sp31 tdor sdo x data output rise time (4) ? ? ? ns see parameter d031 sp35 tsch2dov, tscl2dov sdo x data output valid after sck x edge ??30ns ? sp36 tdov2sc, tdov2scl sdo x data output setup to first sck x edge 30 ? ? ns ? sp40 tdiv2sch, tdiv2scl setup time of sdi x data input to sck x edge 20 ? ? ns ? sp41 tsch2dil, ts c l 2 d i l hold time of sdi x data input to sck x edge 20 ? ? ns ? note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: the minimum clock period for sck is 100 ns. therefore, the clock generated in master mode must not violate this specification. 4: assumes 50 pf load on all spi pins. ss x sck x (ckp = 0 ) sck x (ckp = 1 ) sdo x sdi sp50 sp40 sp41 sp30,sp31 sp51 sp35 sdi x msb lsb bit14 - - - - - -1 msb in bit14 - - - -1 lsb in sp52 sp73 sp72 sp72 sp73 sp71 sp70 note: refer to figure 23-3 for load conditions.
? 2006 microchip technology inc. ds70117f-page 199 dspic30f6011/6012/6013/6014 table 23-33: spi module slave mode (cke = 0 ) timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions sp70 tscl sck x input low time 30 ? ? ns ? sp71 tsch sck x input high time 30 ? ? ns ? sp72 tscf sck x input fall time (3) ?1025ns ? sp73 tscr sck x input rise time (3) ?1025ns ? sp30 tdof sdo x data output fall time (3) ? ? ? ns see parameter d032 sp31 tdor sdo x data output rise time (3) ? ? ? ns see parameter d031 sp35 tsch2dov, tscl2dov sdo x data output valid after sck x edge ? ? 30 ns ? sp40 tdiv2sch, tdiv2scl setup time of sdi x data input to sck x edge 20 ? ? ns ? sp41 tsch2dil, tsc l2 di l hold time of sdi x data input to sck x edge 20 ? ? ns ? sp50 tssl2sch, tssl2scl ss x to sck x or sck x input 120 ? ? ns ? sp51 tssh2doz ss x to sdo x output hi-impedance (3) 10 ? 50 ns ? sp52 tsch2ssh tscl2ssh ss x after sck edge 1.5 t cy + 40 ??ns ? note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: assumes 50 pf load on all spi pins.
dspic30f6011/6012/6013/6014 ds70117f-page 200 ? 2006 microchip technology inc. figure 23-17: spi module slave mode (cke = 1 ) timing characteristics table 23-34: spi module slave mode (cke = 1 ) timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions sp70 tsc l sck x input low time 30 ? ? ns ? sp71 tsch sck x input high time 30 ? ? ns ? sp72 tscf sck x input fall time (3) ?1025ns ? sp73 tscr sck x input rise time (3) ?1025ns ? sp30 tdof sdo x data output fall time (3) ? ? ? ns see parameter d032 sp31 tdor sdo x data output rise time (3) ? ? ? ns see parameter d031 sp35 tsch2dov, tscl2dov sdo x data output valid after sck x edge ??30ns ? sp40 tdiv2sch, tdiv2scl setup time of sdi x data input to sck x edge 20 ? ? ns ? sp41 tsch2dil, tscl2dil hold time of sdi x data input to sck x edge 20 ? ? ns ? note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: the minimum clock period for sck is 100 ns. therefore, the clock generated in master mode must not violate this specification. 4: assumes 50 pf load on all spi pins. ss x sck x (ckp = 0 ) sck x (ckp = 1 ) sdo x sdi sp50 sp60 sdi x sp30,sp31 msb bit14 - - - - - -1 lsb sp51 msb in bit14 - - - -1 lsb in sp35 sp52 sp52 sp73 sp72 sp72 sp73 sp71 sp70 sp40 sp41 note: refer to figure 23-3 for load conditions.
? 2006 microchip technology inc. ds70117f-page 201 dspic30f6011/6012/6013/6014 figure 23-18: i 2 c? bus start/stop bits timing characteristics (master mode) figure 23-19: i 2 c? bus data timing characteristics (master mode) sp50 tssl2sch, tssl2scl ss x to sck x or sck x input 120 ? ? ns ? sp51 tssh2doz ss to sdo x output hi-impedance (4) 10 ? 50 ns ? sp52 tsch2ssh tscl2ssh ss x after sck x edge 1.5 t cy + 40 ? ? ns ? sp60 tssl2dov sdo x data output valid after ss x edge ??50ns ? table 23-34: spi module slave mode (cke = 1 ) timing requirements (continued) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. 3: the minimum clock period for sck is 100 ns. therefore, the clock generated in master mode must not violate this specification. 4: assumes 50 pf load on all spi pins. im31 im34 scl sda start condition stop condition im30 im33 note: refer to figure 23-3 for load conditions. im11 im10 im33 im11 im10 im20 im26 im25 im40 im40 im45 im21 scl sda in sda out note: refer to figure 23-3 for load conditions.
dspic30f6011/6012/6013/6014 ds70117f-page 202 ? 2006 microchip technology inc. table 23-35: i 2 c? bus data timing requirements (master mode) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min (1) max units conditions im10 t lo : scl clock low time 100 khz mode t cy /2 (brg + 1) ? s? 400 khz mode t cy /2 (brg + 1) ? s? 1 mhz mode (2) t cy /2 (brg + 1) ? s? im11 t hi : scl clock high time 100 khz mode t cy /2 (brg + 1) ? s? 400 khz mode t cy /2 (brg + 1) ? s? 1 mhz mode (2) t cy /2 (brg + 1) ? s? im20 t f : scl sda and scl fall time 100 khz mode ? 300 ns c b is specified to be from 10 to 400 pf 400 khz mode 20 + 0.1 c b 300 ns 1 mhz mode (2) ? 100 ns im21 t r : scl sda and scl rise time 100 khz mode ? 1000 ns c b is specified to be from 10 to 400 pf 400 khz mode 20 + 0.1 c b 300 ns 1 mhz mode (2) ? 300 ns im25 t su : dat data input setup time 100 khz mode 250 ? ns ? 400 khz mode 100 ? ns 1 mhz mode (2) tbd ? ns im26 t hd : dat data input hold time 100 khz mode 0 ? ns ? 400 khz mode 0 0.9 s 1 mhz mode (2) tbd ? ns im30 t su : sta start condition setup time 100 khz mode t cy /2 (brg + 1) ? s only relevant for repeated start condition 400 khz mode t cy /2 (brg + 1) ? s 1 mhz mode (2) t cy /2 (brg + 1) ? s im31 t hd : sta start condition hold time 100 khz mode t cy /2 (brg + 1) ? s after this period the first clock pulse is generated 400 khz mode t cy /2 (brg + 1) ? s 1 mhz mode (2) t cy /2 (brg + 1) ? s im33 t su : sto stop condition setup time 100 khz mode t cy /2 (brg + 1) ? s? 400 khz mode t cy /2 (brg + 1) ? s 1 mhz mode (2) t cy /2 (brg + 1) ? s im34 t hd : sto stop condition 100 khz mode t cy /2 (brg + 1) ? ns ? hold time 400 khz mode t cy /2 (brg + 1) ? ns 1 mhz mode (2) t cy /2 (brg + 1) ? ns im40 t aa : scl output valid from clock 100 khz mode ? 3500 ns ? 400 khz mode ? 1000 ns ? 1 mhz mode (2) ??ns ? im45 t bf : sda bus free time 100 khz mode 4.7 ? s time the bus must be free before a new transmission can start 400 khz mode 1.3 ? s 1 mhz mode (2) tbd ? s im50 c b bus capacitive loading ? 400 pf note 1: brg is the value of the i 2 c baud rate generator. refer to the ?inter-integrated circuit? (i 2 c)? section in the ? dspic30f family reference manual? (ds70046) . 2: maximum pin capacitance = 10 pf for all i 2 c pins (for 1 mhz mode only).
? 2006 microchip technology inc. ds70117f-page 203 dspic30f6011/6012/6013/6014 figure 23-20: i 2 c? bus start/stop bits timing characteristics (slave mode) figure 23-21: i 2 c? bus data timing characteristics (slave mode) table 23-36: i 2 c? bus data timing requirements (slave mode) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min max units conditions is10 t lo : scl clock low time 100 khz mode 4.7 ? s device must operate at a minimum of 1.5 mhz 400 khz mode 1.3 ? s device must operate at a minimum of 10 mhz. 1 mhz mode (1) 0.5 ? s? is11 t hi : scl clock high time 100 khz mode 4.0 ? s device must operate at a minimum of 1.5 mhz 400 khz mode 0.6 ? s device must operate at a minimum of 10 mhz 1 mhz mode (1) 0.5 ? s? is20 t f : scl sda and scl fall time 100 khz mode ? 300 ns c b is specified to be from 10 to 400 pf 400 khz mode 20 + 0.1 c b 300 ns 1 mhz mode (1) ? 100 ns is21 t r : scl sda and scl rise time 100 khz mode ? 1000 ns c b is specified to be from 10 to 400 pf 400 khz mode 20 + 0.1 c b 300 ns 1 mhz mode (1) ? 300 ns note 1: maximum pin capacitance = 10 pf for all i 2 c pins (for 1 mhz mode only). is31 is34 scl sda start condition stop condition is30 is33 is30 is31 is33 is11 is10 is20 is26 is25 is40 is40 is45 is21 scl sda in sda out
dspic30f6011/6012/6013/6014 ds70117f-page 204 ? 2006 microchip technology inc. is25 t su : dat data input setup time 100 khz mode 250 ? ns ? 400 khz mode 100 ? ns 1 mhz mode (1) 100 ? ns is26 t hd : dat data input hold time 100 khz mode 0 ? ns ? 400 khz mode 0 0.9 s 1 mhz mode (1) 00.3 s is30 t su : sta start condition setup time 100 khz mode 4.7 ? s only relevant for repeated start condition 400 khz mode 0.6 ? s 1 mhz mode (1) 0.25 ? s is31 t hd : sta start condition hold time 100 khz mode 4.0 ? s after this period the first clock pulse is generated 400 khz mode 0.6 ? s 1 mhz mode (1) 0.25 ? s is33 t su : sto stop condition setup time 100 khz mode 4.7 ? s? 400 khz mode 0.6 ? s 1 mhz mode (1) 0.6 ? s is34 t hd : sto stop condition 100 khz mode 4000 ? ns ? hold time 400 khz mode 600 ? ns 1 mhz mode (1) 250 ns is40 t aa : scl output valid from clock 100 khz mode 0 3500 ns ? 400 khz mode 0 1000 ns 1 mhz mode (1) 0 350 ns is45 t bf : sda bus free time 100 khz mode 4.7 ? s time the bus must be free before a new transmission can start 400 khz mode 1.3 ? s 1 mhz mode (1) 0.5 ? s is50 c b bus capacitive loading ? 400pf ? table 23-36: i 2 c? bus data timing requirements (slave mode) (continued) ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min max units conditions note 1: maximum pin capacitance = 10 pf for all i 2 c pins (for 1 mhz mode only).
? 2006 microchip technology inc. ds70117f-page 205 dspic30f6011/6012/6013/6014 figure 23-22: can module i/o timing characteristics table 23-37: can module i/o timing requirements ac characteristics standard operating conditions: 2.5v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic (1) min typ (2) max units conditions ca10 tiof port output fall time ? ? ? ns see parameter d032 ca11 tior port output rise time ? ? ? ns see parameter d031 ca20 tcwf pulse width to trigger can wake-up filter 500 ns ? note 1: these parameters are characterized but not tested in manufacturing. 2: data in ?typ? column is at 5v, 25c unless otherwise stated. parameters are for design guidance only and are not tested. c x t x pin (output) ca10 ca11 old value new value ca20 c x r x pin (input)
dspic30f6011/6012/6013/6014 ds70117f-page 206 ? 2006 microchip technology inc. table 23-38: 12-bit adc module specifications ac characteristics standard operating conditions: 2.7v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min. typ max. units conditions device supply ad01 av dd module v dd supply greater of v dd - 0.3 or 2.7 ? lesser of v dd + 0.3 or 5.5 v? ad02 av ss module v ss supply v ss - 0.3 ? v ss + 0.3 v ? reference inputs ad05 v refh reference voltage high av ss + 2.7 ? av dd v? ad06 v refl reference voltage low av ss ?av dd - 2.7 v ? ad07 v ref absolute reference voltage av ss - 0.3 ? av dd + 0.3 v ? ad08 i ref current drain ? 180 .001 300 2 a a a/d operating a/d off analog input (1) ad10 v inh -v inl full-scale input span v refl v refh vsee note 1 ad11 v in absolute input voltage av ss - 0.3 av dd + 0.3 v ? ad12 ? leakage current ? 0.001 0.610 av inl = av ss = v refl = 0v, av dd = v refh = 5v source impedance = 2.5 k ad13 ? leakage current ? 0.001 0.610 av inl = av ss = v refl = 0v, av dd = v refh = 3v source impedance = 2.5 k ad17 r in recommended impedance of analog voltage source ? ? 2.5k ? dc accuracy (1) ad20 nr resolution 12 data bits bits ad21 inl integral nonlinearity (2) ??<1lsbv inl = av ss = v refl = 0v, av dd = v refh = 5v ad21a inl integral nonlinearity (2) ??<1lsbv inl = av ss = v refl = 0v, av dd = v refh = 3v ad22 dnl differential nonlinearity (2) ??<1lsbv inl = av ss = v refl = 0v, av dd = v refh = 5v ad22a dnl differential nonlinearity (2) ??<1lsbv inl = av ss = v refl = 0v, av dd = v refh = 3v ad23 g err gain error (2) +1.25 +1.5 +3 lsb v inl = av ss = v refl = 0v, av dd = v refh = 5v ad23a g err gain error (2) +1.25 +1.5 +3 lsb v inl = av ss = v refl = 0v, av dd = v refh = 3v ad24 e off offset error -2 -1.5 -1.25 lsb v inl = av ss = v refl = 0v, av dd = v refh = 5v note 1: these parameters are characterized but not tested in manufacturing. 2: measurements taken with external v ref + and v ref - used as the adc voltage references. 3: the a/d conversion result never decreases with an increase in the input voltage, and has no missing codes.
? 2006 microchip technology inc. ds70117f-page 207 dspic30f6011/6012/6013/6014 ad24a e off offset error -2 -1.5 -1.25 lsb v inl = av ss = v refl = 0v, av dd = v refh = 3v ad25 ? monotonicity (3) ? ? ? ? guaranteed dynamic performance ad30 thd total harmonic distortion ? -71 ? db ? ad31 sinad signal to noise and distortion ?68? db ? ad32 sfdr spurious free dynamic range ?83? db ? ad33 f nyq input signal bandwidth ? ? 100 khz ? ad34 enob effective number of bits 10.95 11.1 ? bits ? table 23-38: 12-bit adc module specifications (continued) ac characteristics standard operating conditions: 2.7v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min. typ max. units conditions note 1: these parameters are characterized but not tested in manufacturing. 2: measurements taken with external v ref + and v ref - used as the adc voltage references. 3: the a/d conversion result never decreases with an increase in the input voltage, and has no missing codes.
dspic30f6011/6012/6013/6014 ds70117f-page 208 ? 2006 microchip technology inc. figure 23-23: 12-bit a/d conversion timing characteristics (asam = 0 , ssrc = 000 ) ad55 t samp clear samp set samp ad61 adclk instruction samp ch0_dischrg ch0_samp ad60 done adif adres( 0 ) 1 2 3 4 5 6 8 7 1 ? software sets adcon. samp to start sampling. 2 ? sampling starts after discharge period. 3 ? software clears adcon. samp to start conversion. 4 ? sampling ends, conversion sequence starts. 5 ? convert bit 11. 9 ? one t ad for end of conversion. ad50 eoc 9 6 ? convert bit 10. 7 ? convert bit 1. 8 ? convert bit 0. execution t samp is described in the ? dspic30f family reference manual ? (ds70046), section 18.
? 2006 microchip technology inc. ds70117f-page 209 dspic30f6011/6012/6013/6014 table 23-39: 12-bit a/d conversion timing requirements ac characteristics standard operating conditions: 2.7v to 5.5v (unless otherwise stated) operating temperature -40c t a +85c for industrial -40 c t a +125c for extended param no. symbol characteristic min. typ max. units conditions clock parameters ad50 t ad a/d clock period ? 334 ? ns v dd = 3-5.5v (note 1) ad51 t rc a/d internal rc oscillator period 1.2 1.5 1.8 s? conversion rate ad55 t conv conversion time ? 14 t ad ?ns ? ad56 f cnv throughput rate ? 200 ? ksps v dd = v ref = 3-5.5v ad57 t samp sample time ? 1 t ad ?nsv dd = 3-5.5v source resistance rs = 0-2.5 k timing parameters ad60 t pcs conversion start from sample trigger ?1 t ad ?ns ? ad61 t pss sample start from setting sample (samp) bit 0.5 t ad ?1.5 t ad ns ? ad62 t css conversion completion to sample start (asam = 1 ) ?0.5 t ad ?ns ? ad63 t dpu time to stabilize analog stage from a/d off to a/d on ?20? s? note 1: because the sample caps will eventually lose charge, clock rates below 10 khz can affect linearity performance, especially at elevated temperatures.
dspic30f6011/6012/6013/6014 ds70117f-page 210 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 211 dspic30f6011/6012/6013/6014 24.0 packaging information 24.1 package marking information xxxxxxxxxxxx xxxxxxxxxxxx yywwnnn 64-lead tqfp (14x14x1mm) dspic30f6011 -30i/pf 041444r example xxxxxxxxxxxx xxxxxxxxxxxx yywwnnn 80-lead tqfp (14x14x1mm) dspic30f6014 -30i/pf 041444r example legend: xx...x customer-specific information y year code (last digit of calendar year) yy year code (last 2 digits of calendar year) ww week code (week of january 1 is week ?01?) nnn alphanumeric traceability code pb-free jedec designator for matte tin (sn) * this package is pb-free. the pb-free jedec designator ( ) can be found on the outer packaging for this package. note : in the event the full microchip part number cannot be marked on one line, it will be carried over to the next line, thus limiting the number of available characters for customer-specific information. 3 e 3 e 3 e 3 e
dspic30f6011/6012/6013/6014 ds70117f-page 212 ? 2006 microchip technology inc. 64-lead plastic thin quad flatpack (pf) 14x14x1 mm body, 1.0/0.10 mm lead form (tqfp) note: for the most current package drawings, please see the microchip packaging specification located at http://www.microchip.com/packaging a2 a1 a c (f) l d e #leads = n1 e1 p b d1 n 1 2 dimensions d1 and e1 do not include mold flash or protrusions. mold flash or protrusions shall not exceed .010" (0.254mm) per side. .630 bsc nom inches .630 bsc .551 bsc .551 bsc overall width overall length foot angle foot length pins per side overall height number of pins lead width drawing no. c04-066 lead thickness molded package thickness * controlling parameter jedec equivalent: ms-026 mold draft angle bottom mold draft angle top molded package width molded package length footprint notes: pitch standoff 11 dimension limits b d1 e1 c d e (f) l 11 .012 .004 .018 0 min a a1 a2 n1 p units n .037 .002 12 11 12 13 12 .015 3.5 .039 ref .024 .018 .008 13 .030 7 16 .031 bsc .039 64 .041 .006 .047 max 16.00 bsc 16.00 bsc 14.00 bsc 14.00 bsc 0.30 0.09 11 0.45 0 0.37 12 1.00 ref 0.60 3.5 millimeters * 0.95 0.05 min 0.80 bsc 1.00 16 nom 64 13 0.45 0.20 13 0.75 7 1.05 0.15 1.20 max revised 7-20-06 bsc: basic dimension. theoretically exact value shown without tolerances. see asme y14.5m
? 2006 microchip technology inc. ds70117f-page 213 dspic30f6011/6012/6013/6014 80-lead plastic thin quad flatpack (pf) 14x14x1 mm body, 1.0/0.10 mm lead form (tqfp) note: for the most current package drawings, please see the microchip packaging specification located at http://www.microchip.com/packaging d e1 #leads = n1 p b l c 2 n 1 (f) a a1 a2 e d1 dimensions d1 and e1 do not include mold flash or protrusions. mold flash or protrusions shall not exceed .010" (0.254mm) per side. .630 bsc nom inches .630 bsc .551 bsc .551 bsc overall width overall length foot angle foot length pins per side overall height number of pins lead width revised 7-20-06 lead thickness molded package thickness * controlling parameter jedec equivalent: ms-026 mold draft angle bottom mold draft angle top molded package width molded package length footprint notes: pitch standoff dimension limits b d1 e1 c d e f l 11 .011 .004 .018 0 min a a1 a2 n1 p units n .037 .002 12 .013 3.5 .039 ref. .024 .015 .008 13 .030 7 20 .026 .039 80 .041 .006 .047 max 16.00 bsc 16.00 bsc 14.00 bsc 14.00 bsc 0.27 0.09 0.45 0 0.32 1.00 ref. 0.60 3.5 millimeters* 0.95 0.05 min 0.65 1.00 20 nom 80 0.37 0.20 0.75 7 1.05 0.15 1.20 max 13 12 11 12 11 11 13 12 13 ref: reference dimension, usually without tolerance, for information purposes only. bsc: basic dimension. theoretically exact value shown without tolerances. see asme y14.5m see asme y14.5m drawing no. c04-116
dspic30f6011/6012/6013/6014 ds70117f-page 214 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70117f-page 215 dspic30f6011/6012/6013/6014 appendix a: revision history revision f (november 2006) previous versions of this data sheet contained advance or preliminary information. they were distrib- uted with incomplete characterization data. revision f of this document reflects the following updates: ? supported i 2 c slave addresses (see table 15-1) ? adc conversion clock selection to allow 200 khz sampling rate (see section 19.0 ?12-bit analog- to-digital converter (a/d) module? ) ? operating current (idd) specifications (see table 23-5) ? bor voltage limits (see table 23-11) ? i/o pin input specifications (see table 23-8) ? watchdog timer time-out limits (see table 23-21)
dspic30f6011/6012/6013/6014 ds70117f-page 216 ? 2006 microchip technology inc. notes:
? 2006 microchip technology inc. ds70143c-page 217 dspic30f6011a/6012a/6013a/6014a index a a/d .................................................................................... 135 aborting a conversion .............................................. 137 adchs register ....................................................... 135 adcon1 register..................................................... 135 adcon2 register..................................................... 135 adcon3 register..................................................... 135 adcssl register ..................................................... 135 adpcfg register..................................................... 135 configuring analog port pins.............................. 64, 143 connection considerations....................................... 143 conversion operation ............................................... 136 effects of a reset...................................................... 142 operation during cpu idle mode ............................. 142 operation during cpu sleep mode.......................... 142 output formats ......................................................... 142 power-down modes .................................................. 142 programming the sample trigger............................. 137 register map............................................................. 144 result buffer ............................................................. 136 sampling requirements............................................ 141 selecting the conversion sequence......................... 136 ac characteristics ............................................................ 182 load conditions ........................................................ 182 ac temperature and voltage specifications .................... 182 ac-link mode operation .................................................. 132 16-bit mode ............................................................... 132 20-bit mode ............................................................... 132 adc selecting the conversion clock ................................ 137 adc conversion speeds .................................................. 138 address generator units .................................................... 39 alternate vector table ........................................................ 49 analog-to-digital converter. see a/d. assembler mpasm assembler................................................... 170 automatic clock stretch...................................................... 98 during 10-bit addressing (stren = 1)....................... 98 during 7-bit addressing (stren = 1)......................... 98 receive mode ............................................................. 98 transmit mode ............................................................ 98 b band gap start-up time requirements............................................................ 188 timing characteristics .............................................. 188 barrel shifter ....................................................................... 23 bit-reversed addressing .................................................... 42 example ...................................................................... 43 implementation ........................................................... 42 modifier values table ................................................. 43 sequence table (16-entry)......................................... 43 block diagrams 12-bit a/d functional ................................................ 135 16-bit timer1 module .................................................. 70 16-bit timer2............................................................... 75 16-bit timer3............................................................... 75 16-bit timer4............................................................... 80 16-bit timer5............................................................... 80 32-bit timer2/3............................................................ 74 32-bit timer4/5............................................................ 79 can buffers and protocol engine............................. 112 dci module ............................................................... 126 dedicated port structure ............................................ 63 dsp engine ................................................................ 20 dspic30f6011/6012/6013/6014................................. 10 dspic30f6013/6014................................................... 11 external power-on reset circuit .............................. 153 i 2 c .............................................................................. 96 input capture mode.................................................... 83 oscillator system...................................................... 147 output compare mode ............................................... 87 reset system ........................................................... 151 shared port structure................................................. 64 spi.............................................................................. 92 spi master/slave connection..................................... 92 uart receiver......................................................... 104 uart transmitter..................................................... 103 bor characteristics ......................................................... 181 bor. see brown-out reset. brown-out reset characteristics.......................................................... 180 timing requirements ............................................... 187 c c compilers mplab c18.............................................................. 170 mplab c30.............................................................. 170 can module ..................................................................... 111 baud rate setting .................................................... 116 can1 register map.................................................. 118 frame types ............................................................ 111 i/o timing characteristics ........................................ 205 i/o timing requirements.......................................... 205 message reception.................................................. 114 message transmission............................................. 115 modes of operation .................................................. 113 overview................................................................... 111 clko and i/o timing characteristics.......................................................... 186 requirements ........................................................... 186 code examples data eeprom block erase ....................................... 58 data eeprom block write ........................................ 60 data eeprom read.................................................. 57 data eeprom word erase ....................................... 58 data eeprom word write ........................................ 59 erasing a row of program memory ........................... 53 initiating a programming sequence ........................... 54 loading write latches ................................................ 54 code protection ................................................................ 145 core architecture overview..................................................................... 15 cpu architecture overview ................................................ 15 customer change notification service............................. 223 customer notification service .......................................... 223 customer support............................................................. 223
dspic30f6011a/6012a/6013a/6014a ds70143c-page 218 ? 2006 microchip technology inc. d data accumulators and adder/subtractor........................... 21 data space write saturation ...................................... 23 overflow and saturation ............................................. 21 round logic ................................................................ 22 write back................................................................... 22 data address space ........................................................... 31 alignment .................................................................... 34 alignment (figure) ...................................................... 35 effect of invalid memory accesses (table)................. 34 mcu and dsp (mac class) instructions example..... 34 memory map ............................................................... 31 memory map for dspic30f6011/6013 ........................ 32 memory map for dspic30f6012/6014 ........................ 33 near data space ........................................................ 35 software stack............................................................ 35 spaces ........................................................................ 31 width ........................................................................... 34 data converter interface (dci) module ............................ 125 data eeprom memory ...................................................... 57 erasing ........................................................................ 58 erasing, block ............................................................. 58 erasing, word ............................................................. 58 protection against spurious write .............................. 61 reading....................................................................... 57 write verify ................................................................. 61 writing ......................................................................... 59 writing, block .............................................................. 60 writing, word .............................................................. 59 dc characteristics ............................................................ 173 bor .......................................................................... 181 brown-out reset ....................................................... 180 i/o pin input specifications ....................................... 178 i/o pin output specifications .................................... 179 idle current (i idle ) .................................................... 176 low-voltage detect................................................... 179 lvdl ......................................................................... 180 operating current (i dd )............................................. 175 power-down current (i pd ) ........................................ 177 program and eeprom............................................. 181 dci module bit clock generator................................................... 129 buffer alignment with data frames .......................... 131 buffer control ............................................................ 125 buffer data alignment ............................................... 125 buffer length control ................................................ 131 cofs pin .................................................................. 125 csck pin .................................................................. 125 csdi pin ................................................................... 125 csdo mode bit ........................................................ 132 csdo pin ................................................................. 125 data justification control bit ..................................... 130 device frequencies for common codec csck frequencies (table)............................... 129 digital loopback mode ............................................. 132 enable ....................................................................... 127 frame sync generator ............................................. 127 frame sync mode control bits ................................. 127 i/o pins ..................................................................... 125 interrupts................................................................... 132 introduction ............................................................... 125 master frame sync operation .................................. 127 operation .................................................................. 127 operation during cpu idle mode ............................. 132 operation during cpu sleep mode .......................... 132 receive slot enable bits .......................................... 130 receive status bits................................................... 131 register map ............................................................ 134 sample clock edge control bit ................................ 130 slave frame sync operation.................................... 128 slot enable bits operation with frame sync............ 130 slot status bits ......................................................... 132 synchronous data transfers .................................... 130 timing characteristics ac-link mode................................................... 195 multichannel, i 2 s modes................................... 193 timing requirements ac-link mode................................................... 195 multichannel, i 2 s modes................................... 194 transmit slot enable bits ......................................... 130 transmit status bits.................................................. 131 transmit/receive shift register ............................... 125 underflow mode control bit...................................... 132 word size selection bits .......................................... 127 development support ....................................................... 169 device configuration register map ............................................................ 159 device configuration registers fborpor ................................................................ 157 fgs .......................................................................... 157 fosc........................................................................ 157 fwdt ....................................................................... 157 device overview................................................................... 9 disabling the uart .......................................................... 105 divide support .................................................................... 18 instructions (table) ..................................................... 18 dsp engine ........................................................................ 19 multiplier ..................................................................... 21 dual output compare match mode .................................... 88 continuous pulse mode.............................................. 88 single pulse mode...................................................... 88 e electrical characteristics .................................................. 173 ac............................................................................. 182 dc ............................................................................ 173 enabling and setting up uart setting up data, parity and stop bit selections ....... 105 enabling the uart ........................................................... 105 equations adc conversion clock ............................................. 137 baud rate................................................................. 107 bit clock frequency.................................................. 129 cofsg period.......................................................... 127 serial clock rate ...................................................... 100 time quantum for clock generation ........................ 117 errata .................................................................................... 8 external clock timing characteristics type a, b and c timer ............................................. 189 external clock timing requirements ............................... 183 type a timer ............................................................ 189 type b timer ............................................................ 190 type c timer ............................................................ 190 external interrupt requests ................................................ 49
? 2006 microchip technology inc. ds70143c-page 219 dspic30f6011a/6012a/6013a/6014a f fast context saving............................................................ 49 flash program memory ...................................................... 51 control registers ........................................................ 52 nvmadr ............................................................ 52 nvmadru.......................................................... 52 nvmcon ............................................................ 52 nvmkey............................................................. 52 i i/o pin specifications input .......................................................................... 178 output ....................................................................... 179 i/o ports .............................................................................. 63 parallel (pio) .............................................................. 63 i 2 c 10-bit slave mode operation ........................................ 97 reception.................................................................... 98 transmission............................................................... 97 i 2 c 7-bit slave mode operation .......................................... 97 reception.................................................................... 97 transmission............................................................... 97 i 2 c master mode operation ................................................ 99 baud rate generator................................................ 100 clock arbitration........................................................ 100 multi-master communication, bus collision and bus arbitration ........................................... 100 reception.................................................................... 99 transmission............................................................... 99 i 2 c master mode support ................................................... 99 i 2 c module .......................................................................... 95 addresses ................................................................... 97 bus data timing characteristics master mode ..................................................... 201 slave mode ....................................................... 203 bus data timing requirements master mode ..................................................... 202 slave mode ....................................................... 203 bus start/stop bits timing characteristics master mode ..................................................... 201 slave mode ....................................................... 203 general call address support .................................... 99 interrupts..................................................................... 98 ipmi support ............................................................... 99 operating function description .................................. 95 operation during cpu sleep and idle modes .......... 100 pin configuration ........................................................ 95 programmer?s model................................................... 95 register map............................................................. 101 registers..................................................................... 95 slope control .............................................................. 99 software controlled clock stretching (stren = 1).... 98 various modes ............................................................ 95 i 2 s mode operation .......................................................... 133 data justification....................................................... 133 frame and data word length selection................... 133 idle current (i idle ) ............................................................ 176 in-circuit serial programming (icsp) ......................... 51, 145 input capture (capx) timing characteristics .................. 191 input capture module ......................................................... 83 interrupts..................................................................... 84 register map............................................................... 85 input capture operation during sleep and idle modes ...... 84 cpu idle mode............................................................ 84 cpu sleep mode ........................................................ 84 input capture timing requirements ................................. 191 input change notification module....................................... 67 register map for dspic30f6011/6012 (bits 15-8) ..... 67 register map for dspic30f6011/6012 (bits 7-0) ....... 67 register map for dspic30f6013/6014 (bits 15-8) ..... 67 register map for dspic30f6013/6014 (bits 7-0) ....... 67 instruction addressing modes ............................................ 39 file register instructions ............................................ 39 fundamental modes supported ................................. 39 mac instructions ........................................................ 40 mcu instructions ........................................................ 39 move and accumulator instructions ........................... 40 other instructions ....................................................... 40 instruction set overview................................................................... 164 summary .................................................................. 161 internet address ............................................................... 223 interrupt controller register map .............................................................. 50 interrupt priority .................................................................. 46 interrupt sequence ............................................................. 48 interrupt stack frame................................................. 49 interrupts ............................................................................ 45 l load conditions................................................................ 182 low voltage detect (lvd) ................................................ 156 low-voltage detect characteristics.................................. 179 lvdl characteristics ........................................................ 180 m memory organization ......................................................... 25 core register map ..................................................... 35 microchip internet web site.............................................. 223 modes of operation disable...................................................................... 113 initialization............................................................... 113 listen all messages.................................................. 113 listen only................................................................ 113 loopback .................................................................. 113 normal operation ..................................................... 113 modulo addressing ............................................................. 40 applicability................................................................. 42 operation example..................................................... 41 start and end address ............................................... 41 w address register selection.................................... 41 mplab asm30 assembler, linker, librarian ................... 170 mplab icd 2 in-circuit debugger ................................... 171 mplab ice 2000 high-performance universal in-circuit emulator.................................................... 171 mplab integrated development environment software.. 169 mplab pm3 device programmer .................................... 171 mplab real ice in-circuit emulator system ................ 171 mplink object linker/mplib object librarian ................ 170 n nvm register map .............................................................. 55
dspic30f6011a/6012a/6013a/6014a ds70143c-page 220 ? 2006 microchip technology inc. o oc/pwm module timing characteristics.......................... 192 operating current (i dd )..................................................... 175 oscillator configurations........................................................... 148 fail-safe clock monitor..................................... 149 fast rc (frc) .................................................. 149 initial clock source selection ........................... 148 low power rc (lprc) ..................................... 149 lp oscillator control ......................................... 148 phase locked loop (pll) ................................ 149 start-up timer (ost) ........................................ 148 operating modes (table) .......................................... 146 system overview ...................................................... 145 oscillator selection ........................................................... 145 oscillator start-up timer timing characteristics .............................................. 187 timing requirements ................................................ 187 output compare interrupts ................................................. 89 output compare module..................................................... 87 register map............................................................... 90 timing characteristics .............................................. 191 timing requirements ................................................ 191 output compare operation during cpu idle mode............ 89 output compare sleep mode operation............................. 89 p packaging information ...................................................... 211 marking ..................................................................... 211 peripheral module disable (pmd) registers .................... 158 picstart plus development programmer ..................... 172 pinout descriptions ............................................................. 12 pll clock timing specifications....................................... 184 por. see power-on reset. porta register map for dspic30f6013/6014 ....................... 65 portb register map for dspic30f6011/6012/6013/6014 ..... 65 portc register map for dspic30f6011/6012 ....................... 65 register map for dspic30f6013/6014 ....................... 65 portd register map for dspic30f6011/6012 ....................... 66 register map for dspic30f6013/6014 ....................... 66 portf register map for dspic30f6011/6012 ....................... 66 register map for dspic30f6013/6014 ....................... 66 portg register map for dspic30f6011/6012/6013/6014 ..... 66 power saving modes ........................................................ 156 idle ............................................................................ 157 sleep ......................................................................... 156 sleep and idle ........................................................... 145 power-down current (i pd ) ................................................ 177 power-up timer timing characteristics .............................................. 187 timing requirements ................................................ 187 program address space..................................................... 25 construction ............................................................... 27 data access from program memory using program space visibility .......................... 29 data access from program memory using table instructions ............................................... 28 data access from, address generation ..................... 27 data space window into operation............................ 30 data table access (ls word) .................................... 28 data table access (ms byte)..................................... 29 memory map for dspic30f6011/6013........................ 26 memory map for dspic30f6012/6014........................ 26 table instructions tblrdh ............................................................. 28 tblrdl.............................................................. 28 tblwth............................................................. 28 tblwtl ............................................................. 28 program and eeprom characteristics............................ 181 program counter ................................................................ 16 programmable .................................................................. 145 programmer?s model .......................................................... 16 diagram ...................................................................... 17 programming operations.................................................... 53 algorithm for program flash....................................... 53 erasing a row of program memory............................ 53 initiating the programming sequence......................... 54 loading write latches ................................................ 54 protection against accidental writes to osccon ........... 150 r reader response............................................................. 224 reset ........................................................................ 145, 151 bor, programmable ................................................ 153 brown-out reset (bor)............................................ 145 oscillator start-up timer (ost) ................................ 145 por operating without fscm and pwrt................ 153 with long crystal start-up time ...................... 153 por (power-on reset)............................................. 151 power-on reset (por)............................................. 145 power-up timer (pwrt) .......................................... 145 reset sequence ................................................................. 47 reset sources ............................................................ 47 reset sources brown-out reset (bor).............................................. 47 illegal instruction trap ................................................ 47 trap lockout............................................................... 47 uninitialized w register trap ..................................... 47 watchdog time-out .................................................... 47 reset timing characteristics............................................ 187 reset timing requirements ............................................. 187 rtsp operation ................................................................. 52 run-time self-programming (rtsp) ................................. 51
? 2006 microchip technology inc. ds70143c-page 221 dspic30f6011a/6012a/6013a/6014a s serial peripheral interface. see spi. simple capture event mode ............................................... 83 buffer operation.......................................................... 84 hall sensor mode ....................................................... 84 prescaler..................................................................... 83 timer2 and timer3 selection mode............................ 84 simple oc/pwm mode timing requirements.................. 192 simple output compare match mode................................. 88 simple pwm mode ............................................................. 88 input pin fault protection............................................ 88 period.......................................................................... 89 software simulator (mplab sim)..................................... 170 software stack pointer, frame pointer............................... 16 call stack frame ........................................................ 35 spi ...................................................................................... 91 spi module ......................................................................... 91 framed spi support ................................................... 91 operating function description .................................. 91 operation during cpu idle mode ............................... 93 operation during cpu sleep mode............................ 93 sdox disable ............................................................. 91 slave select synchronization ..................................... 93 spi1 register map...................................................... 94 spi2 register map...................................................... 94 timing characteristics master mode (cke = 0) .................................... 196 master mode (cke = 1) .................................... 197 slave mode (cke = 1) .............................. 198, 200 timing requirements master mode (cke = 0) .................................... 196 master mode (cke = 1) .................................... 198 slave mode (cke = 0) ...................................... 199 slave mode (cke = 1) ...................................... 200 word and byte communication .................................. 91 status bits, their significance and the initialization condition for rcon register, case 1 ...................... 154 status bits, their significance and the initialization condition for rcon register, case 2 ...................... 155 status register ................................................................... 16 symbols used in opcode descriptions............................. 162 system integration ............................................................ 145 register map............................................................. 159 t table instruction operation summary ................................ 51 temperature and voltage specifications ac ............................................................................. 182 timer1 module .................................................................... 69 16-bit asynchronous counter mode ........................... 69 16-bit synchronous counter mode ............................. 69 16-bit timer mode....................................................... 69 gate operation ........................................................... 70 interrupt....................................................................... 71 operation during sleep mode .................................... 70 prescaler..................................................................... 70 real-time clock ......................................................... 71 interrupts............................................................. 71 oscillator operation ............................................ 71 register map............................................................... 72 timer2 and timer3 selection mode .................................... 88 timer2/3 module................................................................. 73 16-bit timer mode ...................................................... 73 32-bit synchronous counter mode............................. 73 32-bit timer mode ...................................................... 73 adc event trigger ..................................................... 76 gate operation ........................................................... 76 interrupt ...................................................................... 76 operation during sleep mode .................................... 76 register map .............................................................. 77 timer prescaler .......................................................... 76 timer4/5 module................................................................. 79 register map .............................................................. 81 timing characteristics a/d conversion low-speed (asam = 0, ssrc = 000) .............. 208 band gap start-up time........................................... 188 can module i/o ....................................................... 205 clko and i/o ........................................................... 186 dci module ac-link mode................................................... 195 multichannel, i 2 s modes................................... 193 external clock .......................................................... 182 i 2 c bus data master mode..................................................... 201 slave mode ...................................................... 203 i 2 c bus start/stop bits master mode..................................................... 201 slave mode ...................................................... 203 input capture (capx)............................................... 191 oc/pwm module...................................................... 192 oscillator start-up timer............ ............................... 187 output compare module .......................................... 191 power-up timer ........................................................ 187 reset ........................................................................ 187 spi module master mode (cke = 0).................................... 196 master mode (cke = 1).................................... 197 slave mode (cke = 0)...................................... 198 slave mode (cke = 1)...................................... 200 type a, b and c timer external clock ..................... 189 watchdog timer ....................................................... 187 timing diagrams can bit..................................................................... 116 frame sync, ac-link start of frame ....................... 128 frame sync, multi-channel mode ............................ 128 i 2 s interface frame sync ......................................... 128 pwm output ............................................................... 89 time-out sequence on power-up (mclr not tied to v dd ), case 1.................................. 152 time-out sequence on power-up (mclr not tied to v dd ), case 2.................................. 152 time-out sequence on power-up (mclr tied to v dd )...................................................... 152 timing diagrams.see timing characteristics
dspic30f6011a/6012a/6013a/6014a ds70143c-page 222 ? 2006 microchip technology inc. timing requirements band gap start-up time ........................................... 188 brown-out reset ....................................................... 187 can module i/o ........................................................ 205 clko and i/o ........................................................... 186 dci module ac-link mode ................................................... 195 multichannel, i 2 s modes ................................... 194 external clock........................................................... 183 i 2 c bus data (master mode)..................................... 202 i 2 c bus data (slave mode)....................................... 203 input capture ............................................................ 191 oscillator start-up timer ........... ................................ 187 output compare module........................................... 191 power-up timer ........................................................ 187 reset......................................................................... 187 simple oc/pwm mode ............................................. 192 spi module master mode (cke = 0) .................................... 196 master mode (cke = 1) .................................... 198 slave mode (cke = 0) ...................................... 199 slave mode (cke = 1) ...................................... 200 type a timer external clock .................................... 189 type b timer external clock .................................... 190 type c timer external clock .................................... 190 watchdog timer........................................................ 187 timing specifications pll clock.................................................................. 184 trap vectors........................................................................ 48 traps ................................................................................... 47 hard and soft .............................................................. 48 sources....................................................................... 47 address error trap ............................................. 47 math error trap................................................... 47 oscillator fail trap.............................................. 48 stack error trap.................................................. 48 u uart module address detect mode ............................................... 107 auto baud support ................................................... 108 baud rate generator ............................................... 107 enabling and setting up ........................................... 105 framing error (ferr) .............................................. 107 idle status................................................................. 107 loopback mode ........................................................ 107 operation during cpu sleep and idle modes .......... 108 overview................................................................... 103 parity error (perr) .................................................. 107 receive break .......................................................... 107 receive buffer (uxrxb) ........................................... 106 receive buffer overrun error (oerr bit) ................ 106 receive interrupt ...................................................... 106 receiving data ......................................................... 106 receiving in 8-bit or 9-bit data mode ....................... 106 reception error handling ......................................... 106 transmit break ......................................................... 106 transmit buffer (uxtxb) .......................................... 105 transmit interrupt ..................................................... 106 transmitting data ..................................................... 105 transmitting in 8-bit data mode................................ 105 transmitting in 9-bit data mode................................ 105 uart1 register map................................................ 109 uart2 register map................................................ 109 uart operation idle mode .................................................................. 108 sleep mode .............................................................. 108 unit id locations .............................................................. 145 universal asynchronous receiver transmitter. see uart. w wake-up from sleep ......................................................... 145 wake-up from sleep and idle ............................................. 49 watchdog timer timing characteristics .............................................. 187 timing requirements................................................ 187 watchdog timer (wdt)............................................ 145, 156 enabling and disabling ............................................. 156 operation .................................................................. 156 www address ................................................................. 223 www, on-line support .................... ................................... 8
? 2006 microchip technology inc. ds70117f-page 223 dspic30f6011/6012/6013/6014 the microchip web site microchip provides online support via our www site at www.microchip.com. this web site is used as a means to make files and information easily available to customers. accessible by using your favorite internet browser, the web site contains the following information: ? product support ? data sheets and errata, application notes and sample programs, design resources, user?s guides and hardware support documents, latest software releases and archived software ? general technical support ? frequently asked questions (faq), technical support requests, online discussion groups, microchip consultant program member listing ? business of microchip ? product selector and ordering guides, latest microchip press releases, listing of seminars and events, listings of microchip sales offices, distributors and factory representatives customer change notification service microchip?s customer notification service helps keep customers current on microchip products. subscribers will receive e-mail notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest. to register, access the microchip web site at www.microchip.com, click on customer change notification and follow the registration instructions. customer support users of microchip products can receive assistance through several channels: ? distributor or representative ? local sales office ? field application engineer (fae) ? technical support customers should contact their distributor, representative or field application engineer (fae) for support. local sales offices are also available to help customers. a listing of sales offices and locations is included in the back of this document. technical support is available through the web site at: http://support.microchip.com
dspic30f6011/6012/6013/6014 ds70117f-page 224 ? 2006 microchip technology inc. reader response it is our intention to provide you with the best documentation possible to ensure successful use of your microchip prod- uct. if you wish to provide your comments on organization, clarity, subject matter, and ways in which our documentation can better serve you, please fax your comments to the technical publications manager at (480) 792-4150. please list the following information, and use this outline to provide us with your comments about this document. to : technical publications manager re: reader response total pages sent ________ from: name company address city / state / zip / country telephone: (_______) _________ - _________ application (optional): would you like a reply? y n device: literature number: questions: fax: (______) _________ - _________ ds70117f dspic30f6011/6012/6013/6014 1. what are the best features of this document? 2. how does this document meet your hardware and software development needs? 3. do you find the organization of this document easy to follow? if not, why? 4. what additions to the document do you think would enhance the structure and subject? 5. what deletions from the document could be made without affecting the overall usefulness? 6. is there any incorrect or misleading information (what and where)? 7. how would you improve this document?
? 2006 microchip technology inc. ds70117f-page 225 dspic30f6011/6012/6013/6014 product identification system to order or obtain information, e.g., on pricing or delivery, refer to the factory or the listed sales office. dspic30f6011at-30i/pf-es example: dspic30f6011at-30i/pf = 30 mips, industrial temp., tqfp package, rev. a trademark architecture flash e = extended high temp -40c to +125c i = industrial -40c to +85c temperature device id package pf = tqfp 14x14 s = die (waffle pack) w = die (wafers) memory size in bytes 0 = romless 1 = 1k to 6k 2 = 7k to 12k 3 = 13k to 24k 4 = 25k to 48k 5 = 49k to 96k 6 = 97k to 192k 7 = 193k to 384k 8 = 385k to 768k 9 = 769k and up custom id (3 digits) or t = tape and reel a,b,c? = revision level engineering sample (es) speed 20 = 20 mips 30 = 30 mips
ds70117f-page 226 ? 2006 microchip technology inc. americas corporate office 2355 west chandler blvd. chandler, az 85224-6199 tel: 480-792-7200 fax: 480-792-7277 technical support: http://support.microchip.com web address: www.microchip.com atlanta alpharetta, ga tel: 770-640-0034 fax: 770-640-0307 boston westborough, ma tel: 774-760-0087 fax: 774-760-0088 chicago itasca, il tel: 630-285-0071 fax: 630-285-0075 dallas addison, tx tel: 972-818-7423 fax: 972-818-2924 detroit farmington hills, mi tel: 248-538-2250 fax: 248-538-2260 kokomo kokomo, in tel: 765-864-8360 fax: 765-864-8387 los angeles mission viejo, ca tel: 949-462-9523 fax: 949-462-9608 santa clara santa clara, ca tel: 408-961-6444 fax: 408-961-6445 toronto mississauga, ontario, canada tel: 905-673-0699 fax: 905-673-6509 asia/pacific asia pacific office suites 3707-14, 37th floor tower 6, the gateway habour city, kowloon hong kong tel: 852-2401-1200 fax: 852-2401-3431 australia - sydney tel: 61-2-9868-6733 fax: 61-2-9868-6755 china - beijing tel: 86-10-8528-2100 fax: 86-10-8528-2104 china - chengdu tel: 86-28-8665-5511 fax: 86-28-8665-7889 china - fuzhou tel: 86-591-8750-3506 fax: 86-591-8750-3521 china - hong kong sar tel: 852-2401-1200 fax: 852-2401-3431 china - qingdao tel: 86-532-8502-7355 fax: 86-532-8502-7205 china - shanghai tel: 86-21-5407-5533 fax: 86-21-5407-5066 china - shenyang tel: 86-24-2334-2829 fax: 86-24-2334-2393 china - shenzhen tel: 86-755-8203-2660 fax: 86-755-8203-1760 china - shunde tel: 86-757-2839-5507 fax: 86-757-2839-5571 china - wuhan tel: 86-27-5980-5300 fax: 86-27-5980-5118 china - xian tel: 86-29-8833-7250 fax: 86-29-8833-7256 asia/pacific india - bangalore tel: 91-80-4182-8400 fax: 91-80-4182-8422 india - new delhi tel: 91-11-4160-8631 fax: 91-11-4160-8632 india - pune tel: 91-20-2566-1512 fax: 91-20-2566-1513 japan - yokohama tel: 81-45-471- 6166 fax: 81-45-471-6122 korea - gumi tel: 82-54-473-4301 fax: 82-54-473-4302 korea - seoul tel: 82-2-554-7200 fax: 82-2-558-5932 or 82-2-558-5934 malaysia - penang tel: 60-4-646-8870 fax: 60-4-646-5086 philippines - manila tel: 63-2-634-9065 fax: 63-2-634-9069 singapore tel: 65-6334-8870 fax: 65-6334-8850 taiwan - hsin chu tel: 886-3-572-9526 fax: 886-3-572-6459 taiwan - kaohsiung tel: 886-7-536-4818 fax: 886-7-536-4803 taiwan - taipei tel: 886-2-2500-6610 fax: 886-2-2508-0102 thailand - bangkok tel: 66-2-694-1351 fax: 66-2-694-1350 europe austria - wels tel: 43-7242-2244-39 fax: 43-7242-2244-393 denmark - copenhagen tel: 45-4450-2828 fax: 45-4485-2829 france - paris tel: 33-1-69-53-63-20 fax: 33-1-69-30-90-79 germany - munich tel: 49-89-627-144-0 fax: 49-89-627-144-44 italy - milan tel: 39-0331-742611 fax: 39-0331-466781 netherlands - drunen tel: 31-416-690399 fax: 31-416-690340 spain - madrid tel: 34-91-708-08-90 fax: 34-91-708-08-91 uk - wokingham tel: 44-118-921-5869 fax: 44-118-921-5820 w orldwide s ales and s ervice 10/19/06
mouser electronics authorized distributor click to view pricing, inventory, delivery & lifecycle information: microchip: ? dspic30f6013t-20e/pf? dspic30f5011-20i/pt? dspic30f6012t-30e/pf? dspic30f6013-20e/pf? dspic30f6012-20e/pf? dspic30f6014-20e/pf? dspic30f6011-20e/pf? dspic30f5011t-30i/pt? dspic30f5013t- 30i/pt? dspic30f6012t-20e/pf? dspic30f6014-30i/pf? dspic30f6011-30i/pf? dspic30f6013-30i/pf? dspic30f6012-30i/pf? dspic30f6011-20i/pf? dspic30f6013-20i/pf? dspic30f6012-20i/pf? dspic30f6014- 20i/pf? dspic30f5013t-20i/pt? dspic30f5011t-20i/pt? dspic30f6012t-30i/pf? dspic30f6014t-30i/pf? dspic30f6013t-30i/pf? dspic30f6011t-30i/pf? dspic30f6014t-20e/pf? dspic30f5013-30i/pt? dspic30f5011- 30i/pt? dspic30f6012-30e/pf? dspic30f6014t-20i/pf? dspic30f6012t-20i/pf? dspic30f6013t-20i/pf? dspic30f6011t-20i/pf? dspic30f6011t-20e/pf? dspic30f6011at-30i/pf? dspic30f6012at-20e/pf? dspic30f6012at-30i/pf? dspic30f6013at-20e/pf? dspic30f6013at-30i/pf? dspic30f6014at-20e/pf? dspic30f6014at-30i/pf? dspic30f6011-20i/pf? dspic30f6013-20i/pf? dspic30f6012-20i/pf? dspic30f6014- 20i/pf? dspic30f5011-20i/pt? dspic30f6013-20e/pf? dspic30f6012-20e/pf? dspic30f6014-20e/pf? dspic30f6011-20e/pf? dspic30f5011t-30i/pt? dspic30f5013t-30i/pt? dspic30f6014-30i/pf? dspic30f6011- 30i/pf? dspic30f6013-30i/pf? dspic30f6012-30i/pf? dspic30f5011t-20i/pt? dspic30f6014t-30i/pf? dspic30f6013t-30i/pf? dspic30f6014t-20e/pf? dspic30f5011-30i/pt? dspic30f6014t-20i/pf? dspic30f6011at-30i/pf? dspic30f6012at-20e/pf? dspic30f6012at-30i/pf? dspic30f6013at-20e/pf? dspic30f6013at-30i/pf? dspic30f6014at-20e/pf? dspic30f6014at-30i/pf

▲Up To Search▲

Price & Availability of DSPIC30F5011-30IPT

	To Download DSPIC30F5011-30IPT Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .